fix(i18n): label the contact name field with its own key

[opastorello]

Summary

The contact Details tab labels the name field with the company key, so it renders "Company" above the name input — and "Company" again above the actual company input. Wrong in English too, not just ko.

What changed

src/components/contacts/contact-detail-view.tsx:491 read:

<Label>{t('company', { fallback: 'Name' })}</Label>
<Input value={editName} onChange={(e) => setEditName(e.target.value)} />

The namespace is Contacts.detailView, so that resolves to Contacts.detailView.company — "Company" / "회사". There is no Contacts.detailView.name key in either catalogue; the { fallback: 'Name' } looks like it covers that, but next-intl's second argument is ICU values, not options — confirmed against the installed 4.13.1 types, where TranslateArgs is [values?, formats?]. So it was silently discarded and the wrong label won.

• messages/en.json — add Contacts.detailView.name = "Name".
• messages/ko.json — add "이름", the term already used for name in six other places in the file.
• contact-detail-view.tsx — point the label at t('name'), and drop the two decorative fallback arguments (:465 had one too, harmless there since the key exists, but it reads like a guard and isn't one).

Worth noting this is a class of drift the parity test from #419 can't catch: both catalogues have company, so key parity is satisfied — the bug is the call site reaching for the wrong key. Flagging it in case it shapes what else is worth guarding.

Test plan

• npm run typecheck clean.
• npm run lint — 39 warnings, same as main, no new ones.
• npm run build succeeds.
• npm test — src/i18n/messages.test.ts passes both directions (no missing keys, no orphans); the 5 failures in currency / date-utils are the known non-UTC/ICU artifacts of a local machine and are identical on main.
• Script-checked every t('…') in the touched file against both catalogues: 34 keys, all resolving in en and ko.
• Not exercised in a browser — the Details tab needs an authenticated session against a live Supabase project. The change is a label key swap covered by the checks above.

Note: messages/en.json, messages/ko.json and contact-detail-view.tsx already fail prettier --check on main, so I left formatting alone rather than bury a two-line fix in a reformat. My additions follow the surrounding style.

Related

Follows the { fallback: … } observation in #418.