[Observability RAC] Meta: Register all observability rules with RAC registry system

[smith]

To satisfy this requirement, each observability app should do the following:

• Register their rule types with the RAC registry system
  • create rule registry that inherits from another rule registry (optional)
  • Add a reason handler
  • Add a url string to the app in the context of the alert (incl. time range, filters, etc.)
  • Specify a landing page that a user is taken to when clicking "View in app" on alerts table

Solutions:

• APM ([APM] Alert reason renderer #96624)
• Logs ([RAC] [Logs UI] Register Logs UI rule types with new RAC rules registry #98379)
• Metrics ([RAC] [Metrics UI] Register Metrics UI rule types with new RAC rules registry #98360)
• Uptime ([RAC] [Uptime UI] Register Uptime UI rule type(s) with new RAC rules registry #98382)
• UX (doesn't have any alerts)

This is related to #95908, which says,

First version will be an "hardcoded" reason defined in the product, users cannot customize it.

These can either be defined at when the rule is registered, or in the table renderers in the observability plugin. The table and flyouts should display and use the text and links.

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[paulb-elastic]

Uptime issue for this: #98382