[ML] Transforms: Improve messages for recovered alerts

[darnautov]

Summary

Updates the transform health alerting rules:

• Removes 100 limit
• Changes format of the alert message
• Mentions recovered transforms in the alert message

Checklist

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[peteharverson]

As discussed, what about limiting the number of IDs we display in the first part of the message to say 10 (?), to say something like

35 transforms are not started: endpoint.metadata_current-default-8.18.0-prerelease.1, endpoint.metadata_united-default-8.18.0-prerelease.1, fq_continuous_latest_transform, fq_response_times_continuous, gallery_latest_transform, transform_a, transform_b, transform_c, transform_d, transform_e and 25 others

If a user really wants to see all the IDs they can loop through each of the IDs usinh the context variables.

[darnautov]

Updated in f36309a

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: f36309a

Failed CI Steps

• Jest Tests #10

Test Failures

• [job] [logs] Jest Tests #10 / useOnSubmit should set incremented name if other package policies exist

Metrics [docs]

✅ unchanged

History

• 💛 Build #264879 was flaky 2843903
• 💔 Build #264771 failed b88f6e9
• 💔 Build #264740 failed c21085f

cc @darnautov