feat(settings): the import preview edits the check-in facts, and the form takes the format's bounds and anchors

[aleskiontherun]

When an import preview carries check_in_details, the import card shows each fact the document carries (date of birth, phone, emergency contact, insurance). The account's current value sits beside the API's proposal, and the proposal is pre-filled in the form module's own fields, so the same bounds, anchor rule and future-date guard apply. Anything left in the boxes goes back as check_in_details on apply. Keep mine leaves a fact out of the submission, and emptying a fact clears it. The card re-reads the signed-in user only when the result carries check_in_detail_written, so the check-in card on the same page never saves stale values back. The form module takes the columns' new bounds and requires a contact's name and an insurance's provider, using the API's own messages. check_in_detail_dropped renders as a warning. The export card's UDDF row now says what that file carries of the diver's details.

Verified with npm run lint, npm run type-check and npm test (unit tests for the form module and submission helpers, render tests for the import card's section, submission, anchor and refresh behaviour).

🤖 Generated with Claude Code