Missing N field in new contacts

Describe the bug

When a new contact is created, you can fill in the name in the title bar. This becomes the FN field.

Many external applications however rely on the content of the N field, even though it is formally optional. To get an N field, the user must explicitly engage the "Detailed Name" property and then fill the fields.

I'd propose to add a setting to automatically add the "Detailed Name" property upon contact creation. Filling it in takes as little time as filling in the name in the title bar. When N is filled, infer FN from N.

Alternatively, but error prone, infer N from FN.

As stated, many external applications rely on the content of the N field so I decided to label this a bug and not an enhancement. Feel free to disagree.

Start by locating the contact-creation flow and the handling of the Detailed Name property in the JavaScript app. Trace how FN and N are populated and serialized for new contacts. Done means the proposed creation behavior is implemented and the resulting contact contains the expected N and FN fields.