Per-record field name for OTP field about passff HOT 4 OPEN

It's a good idea to support entry-specific input names for certain fields. Implementation-wise this would be easiest like this:

AephieryZ2Ya
login: kevin
url: example.com
otpauth://totp/Example:[email protected]?secret=JBSWY3DPEHPK3PXP&issuer=Example
pin: 1234
loginkey: PASSFF_INPUT_OTP
fancyinput: PASSFF_INPUT_LOGIN

Then, if the user tells PassFF to fill the form, it would loop through the "other" fields like it's currently implemented:

 let matching = findIntersection(otherNames, inputNames); 
 if (matching !== undefined) { 
   let value = passwordData._other[matching];
   if (value == "PASSFF_INPUT_OTP") {
     value = passwordData.otp;
   } else if (value == "PASSFF_INPUT_LOGIN") {
     value = passwordData.login;
   } else if (value == "PASSFF_INPUT_PASSWORD") {
     value = passwordData.password;
   }
   writeValueWithEvents(input, value); 
   return; 
 } 

from passff.

This looks great, and while my initial thought was to reuse YAML references, let's not overcomplicate things, especially since we're not using YAML.

The only thing I'll say is s/INPUT/FIELD/ since we're not really talking input, but fields. But either way, this would be great to have, and I'll be the first to test.

from passff.

Either of INPUT or FIELD in the flag name is okay with me. The field name is both the name of a field and of an input. The flag then tells you that the corresponding "input" is actually to be used for a different purpose (like OTP or LOGIN), and it also tells you at the same time to use the value stored in a different "field" (like OTP or LOGIN).

from passff.