[CI] Add Test validation of `autoops_es.yml`

We need to ensure that changes committed to the `autoops_es*.yml` family of OTel configurations do not prevent the agent from starting.

Recently there was a bug where `1d` was specified as the period to align with the other `1*` values (`10s`, `1m`), but unfortunately `d` is not considered a valid unit by the beats config reader for periods.

https://github.com/elastic/elastic-agent/pull/12383

If we had CI validate the config, then this would not have been an issue.

Start by reviewing the autoops_es*.yml configuration family and the change discussed in pull request 12383, then locate the existing agent-start or configuration-validation CI entry point. Done means CI validates these configurations and catches invalid period units such as `1d` before they can prevent the agent from starting.

Written by the indexing model from the issue text.