[Lens][Embeddable] Make Embeddable resilient when toggling actions

[dej611]

Summary

Fix #125262

This PR changes the way the useEmbeddableFactory hook was called when creating the Lens embeddable: the transition between EmbeddableRoot to EmbeddablePanel (and viceversa) was triggering an unmount event which was destroying the inner embeddable object, with no clear way to detect whether it was a transition or a real destroying event because the page was unmounted.

Pushing down the embeddable creation code automatically handles the transition phase as the inner component lifecycle events make it work correctly in case of transition.

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
• 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

[elasticmachine]

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

[dej611]

@elasticmachine merge upstream

[dej611]

@elasticmachine merge upstream

[dej611]

@elasticmachine merge upstream

[dej611]

@elasticmachine merge upstream

[flash1293]

Tested and works, LGTM

[flash1293]

nit unused import

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: fdab14d
• Storybooks Preview
• Webpack Bundle Analyzer

Test Failures

• [job] [logs] Default CI Group #16 / lens app lens runtime fields should be able to add runtime field and use it

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
lens	1.1MB	1.1MB	+1.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
lens	43.6KB	43.8KB	+195.0B

History

• 💚 Build #27910 succeeded 3c2c14b
• 💚 Build #27594 succeeded 4b7fb5b
• 💛 Build #27381 was flaky 71bc301
• 💛 Build #27066 was flaky 78b56d1
• 💚 Build #26724 succeeded e2c2418

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream