fix(admin): name records by translatable (mltext) fields

The record heading, breadcrumb crumb and document title took the first
plain text field only, so records named by an mltext field fell back to
the generic update message. A shared recordDisplayName helper now takes
the first text or ML field and reads its default locale, then the first
non-empty one.

admin/tests/form/FormView.test.ts

@@ -611,6 +611,14 @@ describe('password and preset on the form (UI-SPEC S7, D-19, D-27 G7)', () => {
     expect(editor(wrapper, 'slug').element.value).toBe('ada-lovelace')
   })
 
+  it('titles a record by the default locale of an mltext first field, and publishes it as the crumb', async () => {
+    const record = clone(rosterRecordFixture)
+    record.data.name = { en: 'Ada Lovelace', pl: 'Ada Lovelace PL' }
+    const { wrapper } = await mountApp('/acme/roster/people/1', people({ [`GET ${PEOPLE}/schema/form`]: mlSchema('mltext', 'text'), [`GET ${PERSON}`]: { body: record } }))
+    expect(wrapper.find('h1').text()).toBe('Ada Lovelace')
+    expect(recordCrumb.value).toBe('Ada Lovelace')
+  })
+
   it('drives a text slug from the active locale of an mltext name, until edited', async () => {
     const { wrapper } = await mountApp('/acme/roster/people/create', people({ [`GET ${PEOPLE}/schema/form`]: mlSchema('mltext', 'text') }))
     await editor(wrapper, 'name').setValue('Hello World')