[SLO] Editing an SLO without view_index_metadata on source leaves the SLO in a broken state.

[simianhacker]

Kibana version:

main

Original install method (e.g. download page, yum, from source, etc.):

source

Describe the bug:

When a user, withoutview_index_metadata on the source data, edits an SLO, the transform fails to update and leaves the SLO in a broken state. The SLO saved object definition is updated but the summary, roll-up data, and transform are all deleted.

Steps to reproduce:

Start with a fresh Kibana instance and index data from High Cardinality's fake_stack data

1. Create an SLO with a superuser account, use the elastic user on dev.
2. Create a role that has: the manage_transforms cluster privileges; all on .slo-* index pattern; read on high-* index pattern.
3. Create a user with the role from step 2
4. Login as that user
5. Edit the SLO created in step 1
6. You will end up on the SLO welcome screen without an SLOs listed. The "summary" and "roll-up" indices will be empty, the transform will be missing, and the SLO definition will exist in the saved objects index.

Expected behavior:

We should disable the edit screen when a user doesn't have sufficient privileges on transforms and the source data.

[elasticmachine]

Pinging @elastic/actionable-observability (Team: Actionable Observability)

[kdelemme]

Related to #167938