[Alerting] Update rules detail page to resolve SO IDs if necessary

[ymao1]

Resolve #108074

Summary

This PR:

• Adds an internal resolve HTTP API that calls the saved objects resolve function
• Updates the rule details page to handle 404 Not found errors from the existing GET API and try to resolve those rule IDs using the new internal resolve API. Handling for non-404 errors is unchanged.
• Uses the provided spacesOss UI components to
  • redirect to new URL and show toaster message when resolve outcome is aliasMatch
  • show warning callout when resolve outcome is conflict

To Verify

• Run 7.14 using yarn es snapshot --ssl -E path.data=../data and create some rules, including rules in a non-default space
  • Bookmark or copy the rule details page URLs
    • https://localhost:5601/app/management/insightsAndAlerting/triggersActions/rule/{ruleId}
    • https://localhost:5601/s/new-space/app/management/insightsAndAlerting/triggersActions/rule/{anotherRuleId}
• Switch to this branch and make the following changes: (see Chris's POC PR for example)
  • Change the alerting SO to multiple-isolated and set convertToMultiNamespaceTypeVersion: '8.0.0' in x-pack/plugins/alerting/server/saved_objects/index.ts`
  • Add a dummy migration to x-pack/plugins/alerting/server/saved_objects/migrations.ts

const migrationActions800 = createEsoMigration(
    encryptedSavedObjects,
    (doc: SavedObjectUnsanitizedDoc<RawAlert>): doc is SavedObjectUnsanitizedDoc<RawAlert> => true,
    (doc) => doc // no-op
  );

'8.0.0': executeMigrationWithErrorHandling(migrationActions800, '8.0.0'),

• Run this branch using the same data from 7.14
• Go to the bookmarked URLs from before and make sure your network tab is open
• For rules in the default space, you should see a successful GET request when you go to the bookmarked URL
• For rules in the non-default space, you should see a 404 for the GET and then a successful resolve request when you go to the bookmarked URL. You should be redirected to the rule details page for the updated rule ID and you should see a toaster pop up.
• Not sure how to recreate a conflict outcome but if you want to see the conflict callout, you could modify x-pack/plugins/triggers_actions_ui/public/application/sections/alert_details/components/alert_details_route.tsx to set the outcome to conflict after the resolve call.

Checklist

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

[ymao1]

Left a comment about adding a e2e test for this when the changes are made to the alerting SO to make it share-capable for 8.0

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[YulNaumenko]

LGTM. Works as described.

[ymao1]

@elasticmachine merge upstream

[chrisronline]

LGTM! Great work!

[ymao1]

@elasticmachine merge upstream

[ymao1]

@elasticmachine merge upstream

[ymao1]

@elasticmachine merge upstream

[ymao1]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 5aef051
• Storybooks Preview
• Documentation Changes

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
triggersActionsUi	361	362	+1

Async chunks

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

id	before	after	diff
triggersActionsUi	1.6MB	1.6MB	+2.1KB

Page load bundle

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

id	before	after	diff
triggersActionsUi	89.3KB	89.3KB	+33.0B

Unknown metric groups

API count

id	before	after	diff
alerting	247	248	+1
triggersActionsUi	238	239	+1
total			+2

API count missing comments

id	before	after	diff
alerting	239	240	+1
triggersActionsUi	229	230	+1
total			+2

History

• 💔 Build #146800 failed 01114a3
• 💚 Build #146621 succeeded 56d320c
• 💚 Build #145535 succeeded cb64d77
• 💚 Build #144815 succeeded 47de9e7
• 💚 Build #144790 succeeded 016da6d

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

cc @ymao1

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.x

This backport PR will be merged automatically after passing CI.