[Editor]: Rework action-menu

[cmoinier]

Description

This PR reworks the UI of the action-menu in the dashboard.
It now uses the Angular CDK Overlay like in the import button.

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

[cmoinier]

This test was modified because it was more of an e2e test than a UT, which should test functions and not UI elements.

[jahow]

that makes sense :) although please keep in mind that sometimes unit tests can interact with the DOM too, if there's some logic related to DOM events for instance!

[cmoinier]

Yes! In this case it seemed to me that it was something that could be done (and is already done, actually), in the e2e. I figured it made more sense to test the related logic without all the clicking on the fixture :)

[github-actions]

Affected libs: ui-search, feature-search, feature-router, feature-map, feature-dataviz, feature-record,
Affected apps: metadata-editor, datahub, demo, webcomponents, search, map-viewer,

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

[github-actions]

📷 Screenshots are here!

[coveralls]

coverage: 85.093% (+1.1%) from 83.955%
when pulling 633452d on ME-rework-options-menu
into dbb45b4 on main.

[jahow]

Thank you! The menu works and looks very good.

I think at some point we'll need to factorize all the menu opening code in a separate presentation component, but this can be done later on, especially when we'll want to do the same thing for the rollback confirmation dialog in the editor form:

[cmoinier]

Thank you! The menu works and looks very good.

I think at some point we'll need to factorize all the menu opening code in a separate presentation component, but this can be done later on, especially when we'll want to do the same thing for the rollback confirmation dialog in the editor form:

Right, also since the Import menu works in a very similar way, it would make sense indeed. Let's keep that in mind!