Add Spaces to Dashboard Listing Table

[nickpeihl]

Summary

Related #171461.

Adds the Spaces column to the Dashboard listing page to allow users to easily see and share their dashboards with other Spaces.

I made updates the TableListViewTable shared component to conditionally show the Spaces column. This will allow other applications such as Lens and Maps to also show the Spaces column on their listing pages. The content management mSearch developer example has also been updated to show how other applications could add the Spaces column.

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: 2129e8a
• Interpreting CI Failures

Failed CI Steps

• Check Types and Build API Docs
• FTR Configs #58
• FTR Configs #60
• FTR Configs #60
• FTR Configs #71
• FTR Configs #71
• Post-Build

Test Failures

• [job] [logs] FTR Configs #71 / Agents fleet_list_agent should return metrics if available and called with withMetrics
• [job] [logs] FTR Configs #71 / Agents fleet_list_agent should return metrics if available and called with withMetrics
• [job] [logs] FTR Configs #58 / EPM Endpoints EPM - list list api tests lists all limited packages from the registry
• [job] [logs] FTR Configs #60 / management index management index templates get all should list all the index templates with the expected parameters
• [job] [logs] FTR Configs #60 / management index management index templates get all should list all the index templates with the expected parameters

Metrics [docs]

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

History

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

[nickpeihl]

Closing this as priorities have shifted.