[Uptime] Alerting - Remove Uptime alert state variables from action connectors

[dominiqueclarke]

Relates to #126280

Following #128760, Uptime moved many of its alerting state variables over to context. Although we still need state variables internally for our alerting solution, we should remove references to state variables in user-facing action connectors.

State variables for monitor status alert

• monitorUrl
• monitorId
• monitorName
• monitorType
• latestErrorMessage
• observerLocation
• observerHostname

State variables for TLS alert

• commonName
• issuer
• summary
• status

State variables for anomaly alert

• severity
• severityScore
• anomalyStartTimestamp
• monitor
• monitorUrl
• slowestAnomalyResponse
• expectedResponseTime
• observerLocation
• bucketSpan

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[dominiqueclarke]

After discussion, #126280 (comment), we will remove the state variables from being exposed in the user-facing connectors, while still keeping the variables themselves in tact. Updating AC.