Metadata Editor: Use gnUiEditableLabel directive for title input

[Angi-Kinas]

Description

This PR uses the gnUiEditableLabel directive for the title input.

Screenshots

Todo

• Wait for ME: form field wrapper, abstract record field #854 to move rendering logic to form-field

Quality Assurance Checklist

• Commit history is devoid of any merge commits and readable to facilitate reviews
• If new logic ⚙️ is introduced: unit tests were added
• If new user stories 🤏 are introduced: E2E tests were added
• If new UI components 🕹️ are introduced: corresponding stories in Storybook were created
• If breaking changes 🪚 are introduced: add the breaking change label
• If bugs 🐞 are fixed: add the backport <release branch> label
• The documentation website 📚 has received the love it deserves

---

[github-actions]

Affected libs: feature-editor, ui-layout, feature-dataviz, feature-record, feature-router, feature-catalog, feature-search, feature-map, ui-elements, feature-notifications, ui-catalog, ui-search,
Affected apps: metadata-editor, datafeeder, demo, datahub, webcomponents, map-viewer, search,

• 🚀 Build and deploy storybook and demo on GitHub Pages
• 📦 Build and push affected docker images

[Angi-Kinas]

@LHBruneton-C2C when I was writing a test for this function I realized that this function does the same as handleFieldValueChange. EditorFieldValue can also be a string. So I think we can use handleFieldValueChange as well for the title. WDYT?

[LHBruneton-C2C]

If it's working this way, sure! Sharing the logic is the way to go. Can't remember why this didn't seem to work at first :/

[coveralls]

coverage: 85.163% (+1.4%) from 83.789%
when pulling dd322b5 on editor-record-field-title
into 6083baa on main.

[github-actions]

📷 Screenshots are here!