[Dashboard] Hover actions for panels

[cqliu1]

Summary

Closes #151233.
Closes #175451.
Closes #169677.
Closes #185893.

This updates the design for the actions menu for dashboard panels. With this new design, the most common actions are promoted and available as you hover over the panels.

The remaining actions are available in a context menu similar to the one that exists today but with better organized sections.

Notable changes:

• Switch from context menu in panel title bar to hover actions
• Add groupings to actions for organized sections in actions menu
• Turn off CSS transforms on react-grid-layout
• Hide title bar in edit mode when panel title disabled unless badges or notifications are visible
• Renamed PresentationPanelContextMenu -> PresentationPanelHoverActions
• Promote Explore in Discover action for Lens panels
• Show panel filter notification in view mode and edit mode
• Use discoverApp icon for actions that redirect to Discover

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Flaky Test Runner was used on any tests changed
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[cqliu1]

/ci

[cqliu1]

/ci

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

[roshan-elastic]

Hey @teresaalvarezsoler and folks,

This stuff looks awesome! We're going to pick up the 'Explore in Discover' and drop it into our Lens visualisations in Hosts (and try and build it into other things we touch with Lens too).

A couple of bits of feedback:

1. We're re-adding our custom action to 'Open in Lens' to the ... drop-down which will open the lens visualisation

This is what we had before but we need to re-add it:

Question : For users, being able to open an embedded Lens visualisation as easily as the new hover 'edit' button would be awesome. Can you see this being an option in the future?

Note : We can't allow people to use the 'edit' fly-out functionality as we can't let users save the visualisation back to the current place (e.g. all the host views)

2. We'd like to add the ability for people to 'copy to dashboard'
We were considering doing this but we don't want to invest in the effort of adding this custom action and supporting it:

Question: Do you have any plans to make this a standard option in lens that we could add to our visualisations?

cc @crespocarlos

[teresaalvarezsoler]

Hey @roshan-elastic, we didn't have any plans for these features since we haven't had any requests from solutions until now :) Maybe @ghudgins can sync with you to understand requirements and discuss effort with the team to decide on priorization.

[roshan-elastic]

Sounds good @teresaalvarezsoler cc @ghudgins

We don't have a strong requirement for these yet so wouldn't want to ask you to prioritise them yet - just good to know your plans.

As we look to scale the usage of Lens across O11y, I think we can make a better case for these.