[9.1] (backport #10580) Add monitoring config golden file test for otel runtime

[mergify]

What does this PR do?

Adds an explicit test for the full configuration generated for self-monitoring when using the otel runtime.

Why is it important?

We plan to switch to this runtime by default, so we should have a test checking if the full output of this config generation is valid and stable.

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

Related issues

• Relates [beats receivers] Enable beats receivers for internal monitoring data collection by default #9058

---

This is an automatic backport of pull request #10580 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of a3f71c4 has failed:

On branch mergify/bp/9.1/pr-10580
Your branch is up to date with 'origin/9.1'.

You are currently cherry-picking commit a3f71c40c.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   internal/pkg/agent/application/monitoring/v1_monitor_test.go

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both deleted:    internal/pkg/agent/application/monitoring/component/testdata/monitoring_config_full.yaml
	added by us:     internal/pkg/agent/application/monitoring/testdata/monitoring_config_full.yaml
	added by them:   internal/pkg/agent/application/monitoring/testdata/monitoring_config_full_otel.yaml
	added by them:   internal/pkg/agent/application/monitoring/testdata/monitoring_config_full_process.yaml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[elasticmachine]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: 8d821fd

Failed CI Steps

• Unit tests - Ubuntu 22.04
• Unit tests - Ubuntu 22.04
• Unit tests - Ubuntu 22.04 with requirefips build tag
• Unit tests - Ubuntu 22.04 with requirefips build tag
• Unit tests - fips140=only Ubuntu 22.04
• Unit tests - fips140=only Ubuntu 22.04
• Unit tests - Ubuntu 22.04 ARM64
• Unit tests - Ubuntu 22.04 ARM64
• Unit tests - Windows 2022
• Unit tests - Windows 2022
• Unit tests - Windows 2016
• Unit tests - Windows 2016
• Unit tests - macOS 15 ARM
• Unit tests - macOS 15 ARM
• Unit tests - Windows 10
• Unit tests - Windows 10
• Unit tests - Windows 11
• Unit tests - Windows 11

History

cc @swiatekm