[Alerting] Surface guidance for rules missing an Elastic Cloud API key

[nastasha-solomon]

Summary

Makes the guidance for rules missing an Elastic Cloud API key visible without expanding a dropdown, and updates the tag label to match the current Kibana source:

• Previously, the only guidance for this scenario lived inside the Within 90 days dropdown on Rules and Elastic Cloud API keys in Serverless, framing it as a one-time, post-migration-only check. In reality, a rule can end up missing its Elastic Cloud API key at any time (for example, when created or updated through the public APIs using a personal Elasticsearch API key).
• Pulls this guidance out into a new, always-visible Find rules that are missing an Elastic Cloud API key subsection, placed near the existing note about public-API/personal-key rules.
• Adds a tip inside the Within 90 days dropdown that cross-links to the new subsection, so readers don't assume the check is limited to that window.
• Updates the tag label from the stale Missing Elastic Cloud Api Key to the current Missing Universal Api Key, verified against the MISSING_UIAM_API_KEY_TAG constant in the Kibana source at HEAD. Note: [ResponseOps][Rules] Rename "Missing Universal Api Key" tag to "Missing Elastic Cloud API Key" kibana#283498, which proposes renaming the tag again to "Missing Elastic Cloud API Key," is still open — the docs will need another update if/when that merges.

Fixes #7826.

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes - Cursor

Made with Cursor