dev-tools: add profiling special case for edot

[florianl]

What does this PR do?

#9888 added profiling as an receiver to EDOT. Fix tooling to add this receiver to autogenerated list of components for EDOT.

Why is it important?

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

[mergify]

This pull request does not have a backport label. Could you fix it @florianl? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b edot-profiling-docs upstream/edot-profiling-docs
git merge upstream/main
git push upstream edot-profiling-docs

[elasticmachine]

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

[ycombinator]

The changes in this PR LGTM.

However, I noticed that in #9888 where the profilingreceiver was added, that it's only available on Linux. I wonder if we should add a field to the otelDependency struct to capture which OSes components are available on (defaulting to all OSes, of course). That way we could mention the OS support for each component in the OTel README. This would be done as a follow up PR.

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 6e5b67e

History

• 💔 Build #27782 failed 902b17f
• 💔 Build #27774 failed 2926e18
• 💔 Build #27681 failed c694ed9
• 💚 Build #27516 succeeded f871fa8

cc @florianl