[Shareable Dashboards] Update spaces for new references on save

[cqliu1]

Summary

Feature Branch: #168166
Related to #168241.
Related to #168287

This updates spaces for any new references added to a shared dashboard on save. This currently shares nested panels without any warning to the user that the sharing has occurred. Adding a confirmation modal warning the user that saving will share their newly added references to the same spaces as its parent dashboard in a separate PR.

This also introduced a confirmation modal warning the user when they are saving changes on a shared dashboard.

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

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: 060a4ec
• Interpreting CI Failures

Failed CI Steps

• Build Kibana Distribution and Plugins
• Check Types and Build API Docs
• Jest Tests #8
• Linting
• Linting (with types)
• Checks
• Post-Build

Test Failures

• [job] [logs] Jest Tests #8 / SpaceListInternal using custom properties with the active space, eight inactive spaces, and one unauthorized space with behaviorContext="outside-space", shows badges with button
• [job] [logs] Jest Tests #8 / SpaceListInternal using custom properties with the active space, eight inactive spaces, and one unauthorized space with displayLimit=0, shows badges without button
• [job] [logs] Jest Tests #8 / SpaceListInternal using custom properties with the active space, eight inactive spaces, and one unauthorized space with displayLimit=1, shows badges with button
• [job] [logs] Jest Tests #8 / SpaceListInternal using custom properties with the active space, eight inactive spaces, and one unauthorized space with displayLimit=7, shows badges with button
• [job] [logs] Jest Tests #8 / SpaceListInternal using custom properties with the active space, eight inactive spaces, and one unauthorized space with displayLimit=8, shows badges without button
• [job] [logs] Jest Tests #8 / SpaceListInternal using default properties with "all spaces", the active space, six inactive spaces, and one unauthorized space shows one badge without button
• [job] [logs] Jest Tests #8 / SpaceListInternal using default properties with only "all spaces" shows one badge without button
• [job] [logs] Jest Tests #8 / SpaceListInternal using default properties with the active space and five inactive spaces shows badges without button
• [job] [logs] Jest Tests #8 / SpaceListInternal using default properties with the active space and one inactive space shows one badge without button
• [job] [logs] Jest Tests #8 / SpaceListInternal using default properties with the active space and six inactive spaces shows badges with button
• [job] [logs] Jest Tests #8 / SpaceListInternal using default properties with the active space, five inactive spaces, and one unauthorized space shows badges without button
• [job] [logs] Jest Tests #8 / SpaceListInternal using default properties with the active space, five inactive spaces, and two unauthorized spaces shows badges without button
• [job] [logs] Jest Tests #8 / SpaceListInternal using default properties with the active space, six inactive spaces, and one unauthorized space shows badges with button
• [job] [logs] Jest Tests #8 / SpaceListInternal using default properties with the active space, six inactive spaces, and two unauthorized spaces shows badges with button
• [job] [logs] Jest Tests #8 / SpaceListInternal with a SpacesContext for a specific feature with the active space, eight inactive spaces, and one unauthorized space shows badges with button, showing disabled features at the end of the list

Metrics [docs]

‼️ ERROR: no builds found for mergeBase sha [3e64193]

History

• 💔 Build #179342 failed fe9cf0f
• 💔 Build #175162 failed 3bc73c3
• 💔 Build #174864 failed a130ed0

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