[8.17](backport #4709) Enhancements to alerting docs

[mergify]

Description

Makes some improvements to the alerting docs as suggested by @lucabelluccini:

• List all available alerts with the "real" name in the Kibana (14aace2)
• Prerequisites for APM - Anomaly rule (53df623)
• Guidance on migrating from Uptime to Synthetics (2c53801)
• Suggest the data being queried on each alert type
  • Note: @lucabelluccini mentioned it would be handy to have an hint to which data stream / data view / index pattern each kind of rule uses. E.g. for APM, one might think the user is allowed to use all the data from the traces-apm* data streams, while it's not true. I looked around quite a bit, but I couldn't find a source of truth anywhere. 😕 I'm not sure if that should block the other updates made here.

Documentation sets edited in this PR

Check all that apply.

• Stateful (docs/en/observability/*)
• Serverless (docs/en/serverless/*)
• Integrations Developer Guide (docs/en/integrations/*)
• None of the above

Related issue

Closes #4609

Checklist

• Product/Engineering Review
• Writer Review

Follow-up tasks

Select one.

• This PR does not need to be ported to another doc set because:
  • The concepts in this PR only apply to one doc set (serverless or stateful)
  • The PR contains edits to both doc sets (serverless and stateful)
• This PR needs to be ported to another doc set:
  • Port to stateful docs: <link to PR or tracking issue>
  • Port to serverless docs: <link to PR or tracking issue>

---

This is an automatic backport of pull request #4709 done by [Mergify](https://mergify.com).

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}