chore(ci): Validate catalog-info.yaml

[nuugen]

What does this PR do?

Validate that definitions in catalog-info.yaml are correct.

Why is it important?

To ensure well-formed data ingested into EngProd's tooling.

Checklist

• I have read and understood the pull request guidelines of this project.
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[nuugen]

Build failure is completely expected due to currently malformed catalog-info.yaml. It should be fixed after #7239.

[dliappis]

LGTM

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 3fa703b

History

• 💔 Build #18209 failed 415d3d3

cc @nuugen