[DOCS] Adds machine learning to the security section of alerting (#91501

)

docs/user/alerting/alert-types.asciidoc

@@ -2,7 +2,7 @@
 [[alert-types]]
 == Standard stack alert types
 
-{kib} supplies alert types in two ways: some are built into {kib} (these are known as stack alerts), while domain-specific alert types are registered by {kib} apps such as <<xpack-apm,*APM*>>, <<metrics-app,*Metrics*>>, and <<uptime-app,*Uptime*>>.
+{kib} supplies alert types in two ways: some are built into {kib} (these are known as stack alerts), while domain-specific alert types are registered by {kib} apps such as <<xpack-apm,*APM*>>, <<xpack-ml,*{ml-cap}*>>, <<metrics-app,*Metrics*>>, and <<uptime-app,*Uptime*>>.
 
 This section covers stack alerts. For domain-specific alert types, refer to the documentation for that app.
 Users will need `all` access to the *Stack Alerts* feature to be able to create and edit any of the alerts listed below.

docs/user/alerting/alerting-getting-started.asciidoc

@@ -172,6 +172,7 @@ To access alerting in a space, a user must have access to one of the following f
 * Alerting
 * <<xpack-apm,*APM*>>
 * <<logs-app,*Logs*>>
+* <<xpack-ml,*{ml-cap}*>>
 * <<metrics-app,*Metrics*>>
 * <<xpack-siem,*Security*>>
 * <<uptime-app,*Uptime*>>
@@ -202,4 +203,4 @@ If an alert requires certain privileges to run such as index privileges, keep in
 
 For security reasons you may wish to limit the extent to which {kib} can connect to external services. <<action-settings>> allows you to disable certain <<action-types>> and whitelist the hostnames that {kib} can connect with. 
 
---
+--