EDITOR - Organize fields into pages and sections

[rcaplier]

Description

This PR organize editor fields into pages and sections.

Screenshots

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

---

This work is sponsored by Metadata-editor crowdfunding.

[github-actions]

Affected libs: common-fixtures, api-metadata-converter, api-repository, feature-catalog, feature-record, feature-router, feature-search, feature-map, feature-dataviz, feature-editor, feature-auth, ui-search, ui-elements, feature-notifications, ui-catalog, util-shared, ui-widgets, ui-inputs, ui-layout, ui-map,
Affected apps: metadata-editor, metadata-converter, datahub, demo, webcomponents, search, map-viewer, datafeeder,

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

[github-actions]

📷 Screenshots are here!

[LHBruneton-C2C]

Thanks for this first version!
The code is looking real good, didn't take the time to test.
A few remarks:

• datahub in commit messages => metadata-editor
• I like the new editor configuration, although I find it weird that each record should come with the app config. I don't know how to change it though. Maybe having a dedicated EditorConfig service appart from the fields.

And also, I was told not to put the Jira ticket tag in the PR, as this is public work.

[coveralls]

coverage: 81.552% (-2.0%) from 83.533%
when pulling 6357e36 on me-organize-fields-into-pages-and-sections
into e77c0f8 on main.

[jahow]

This is a first review, I'll take more time to look into the rest.

First, thank you for the extensive work! I like the general approach and I agree that adding a pages > sections > fields hierarchical structure in the config is the right way to go.

As for the editor state, what do you think about storing the active page in the state, then instead of having a selectRecordFields selector, provide a selectEditorSections selector instead? Then the record-form component would get a list of sections according to the current page, and show them including the fields they contain.

That would also mean that the Breadcrumbs (or really page selector) component would be connected to the editor state directly.

[jahow]

Thank you! I've made a few comments for cleaning up things, but apart from that it's good to go.