[Fleet] Make logs-* and metrics-* data views available across all spaces

[kpollich]

Summary

Closes #172009

Adds a call to updateObjectsSpaces with ['*'] as the spaces list after Fleet's managed data views are created.

Existing data views will be updated to be global whenever installKibanaAssets is called.

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[apmmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• /oblt-deploy-serverless : Deploy a serverless Kibana instance using the Observability test environments.
• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 1427c8b

Failed CI Steps

• x-pack/test_serverless/functional/test_suites/observability/config.ts
• Detection Engine - Security Solution Cypress Tests #6

Test Failures

• [job] [logs] Detection Engine - Security Solution Cypress Tests #6 / Alert user assignment - ESS & Serverless Updating assignees (single alert) adding new assignees via More actions in alerts table adding new assignees via More actions in alerts table
• [job] [logs] x-pack/test_serverless/functional/test_suites/observability/config.ts / serverless observability UI Observability Log Explorer Header menu Discover tabs should navigate between discover tabs without keeping the current columns/filters/query/time/data view

Metrics [docs]

✅ unchanged

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

cc @kpollich

[kpollich]

Since this operation gets retried on every setup, there is a possibility this error will appear many times in logs if there is something going wrong with the spaces update operation. Maybe worth moving this to debug?

[nchaulet]

@kpollich what will could make that update fail? any thing that will not be a transient error?

[kpollich]

I think if someone manually creates one of these data views with the same title property before installing any integrations there could be a conflict and that would surface as an error here. Very much an edge case and technically preexisting before this PR.

[nchaulet]

LGTM

[mbudge]

What happens if a data view created by the user called logs or metrics already exists in the space? Don’t want our dashboards to break again.

[kpollich]

Data views have a globally unique ID that must be unique across all spaces, so there should be no risk of conflict when Fleet marks one as global here. Even if there are multiple logs-* and metrics-* patterns in many spaces, Fleet will also only update data views that exist in the current space where an integration is being installed as well.

Overall, this change should allow users to remove their own logs-* and metrics-* data views in favor of the ones managed by Fleet.