[Security Solution] Handle SavedObjects breaking changes for 8.0

[peluja1012]

Related issue: #100489

Before the 8.0 release (during 7.x): Make sure that existing saved object types are using references correctly to link to other objects. If you are linking to other objects and you aren't using the root-level references field, it will break in 8.0.

• [Security Solution][Detections] Migrate to using Saved Object References array to reference Exception Lists from Rules #101975
• [Security Solution][Detections] Migrate to using Saved Object References array to reference alert saved objects from security saved objects #107068
• [Security Solution] [Platform] Alerts with references to pre-8.0 id should be visible in alerts table in rule detail view #118935

Other types of objects that are not Saved Objects, but still will be affected because they reference detection rules which are Saved Objects:

• Existing and future detection alerts in .siem-signals-* and .alerts-security.alerts-* indices.
  • Research approach for RAC when making rules and connectors share-capable #107161
• Future execution events and metrics in Rule Execution Log. This one will be addressed in:
  • [RAC][Security Solution][Detections] Rule Execution Log - technical implementation #101013

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[jportner]

To add to this:

Any "deep linked" pages that use saved object IDs will also need to be updated to use the new resolve() API to retrieve the associated saved object, and handle the three different outcomes. Details are in the meta-issue #100489.

[jportner]

In case anyone is following this issue but not the linked meta-issue (#100489):

I published the Sharing Saved Objects developer guide, please take a look before proceeding with the implementation. And of course, please reach out if you run into any problems!

[yctercero]

Closing this ticket out as work was completed.