[Rule Registry] Updating index.mapping.total_fields.limit index setting on concrete backing indices

[ymao1]

Summary

Upgrade testing on the QA cluster revealed that this PR to add the ECS component template to the observability alerts as data index templates will cause errors during rule registry initialization when the mappings are updated for existing concrete indices for 7.17 that have a total field limit of 1000. While we specify a higher limit in the index template specification, those changes are not applied to existing indices, instead they will apply when the indices roll over. This PR updates this specific index setting for existing concrete indices.

To Verify

1. Run 7.17 and create an observability rule. Make sure that rule becomes active and writes out alerts as data (this ensures that the concrete index is created. Go to the index settings for this concrete index and verify that the total fields limit is 1000.
2. Run this branch using the same ES data and verify there are no rule registry initialization errors during startup. Go to the index settings for the concrete index and verify that the total fields limit has been updated to 1900.

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[ymao1]

@elasticmachine merge upstream

[ymao1]

@elasticmachine merge upstream

[fkanout]

Actionable Observability changes LGTM

[ymao1]

@elasticmachine merge upstream

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: c757b8d

Failed CI Steps

• FTR Configs #6
• FTR Configs #44

Test Failures

• [job] [logs] FTR Configs #6 / Reporting APIs Job parameter validation printablePdfV2 fails if there is an invalid layout ID

Metrics [docs]

✅ unchanged

History

• 💔 Build #81746 failed 62a896d
• 💚 Build #80976 succeeded 2087f1f
• 💚 Build #80702 succeeded 1fd7f3b
• 💚 Build #80565 succeeded 52ca188

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @ymao1

[ersin-erdal]

LGTM