[EDITOR]: Prefill contact informations with current user

[rcaplier]

Description

This PR makes every new record created prefilled with current connected user as contact for resource with role "point_of_contact".

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 **.

[github-actions]

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

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

[github-actions]

📷 Screenshots are here!

[coveralls]

coverage: 83.031% (+1.7%) from 81.367%
when pulling 6e317bc on me-prefill-contact-informations-with-current-user
into 7a893ad on main.

[jahow]

Thank you, great work!!

[jahow]

I think it would be beneficial to agree on a way to write our fixtures. The original approach was to use deepFreeze to avoid mutating fixtures between tests; creating an object each time makes sense too but it'd be better not to mix these practices too much to avoid confusion