feat: move edot in a separate package

[pkoutsovasilis]

What does this PR do?

This PR introduces EDOT (Elastic Distribution for OpenTelemetry) as a separate repository sub-package by moving code from internal/pkg/otel to internal/edot. This is a pure refactoring/relocation change with no functional modifications. Specifically:

• Relocates EDOT code: Moves all EDOT-related code from internal/pkg/otel/* to internal/edot/pkg/*
• Updates all import paths: Changes throughout the codebase from github.com/elastic/elastic-agent/internal/pkg/otel/... to github.com/elastic/elastic-agent/internal/edot/pkg/...
• Maintains functionality: Zero behavioural changes - all existing functionality remains identical
• Preserves internal structure: The internal organisation within EDOT packages remains unchanged
• Updates build system: Adjusts mage targets, namely update:beats, otel:readme, etc., and scripts to reference the new package location
• Updates dependencies: Regenerates go.mod and go.sum to reflect the new import paths

Changes summary: 50 files changed, +53,172 additions, -50,175 deletions (the large diff is primarily due to go.mod/go.sum/NOTICE*.txt regeneration and mechanical import path updates)

Why is it important?

This change is the second step in the incremental approach to separate EDOT from elastic-agent (as outlined in PR #9308). Introducing EDOT as a separate sub-package provides:

1. Clearer separation of concerns: Physically separates EDOT code from elastic-agent control plane code at the repository level, making the architecture explicit
2. Prepares for module separation: Establishes the package structure needed to eventually extract EDOT into its own Go module with a separate go.mod
3. Improves code organization: Makes it immediately clear which code belongs to EDOT vs elastic-agent control plane
4. Simplifies future splitting: Having EDOT in internal/edot/ makes it straightforward to later extract it as a separate module or even repository

This follows the incremental approach decided by the team to split the large PR #9308 into smaller, reviewable chunks.

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

None. This is a pure internal code reorganisation with no changes to functionality, APIs, configuration, or user-facing behaviour. The change is completely transparent to end users.

How to test this PR locally

Since this is a refactoring PR with no functional changes, testing focuses on ensuring everything continues to work as before, everything should work as before. So run any/all unit-test and/or integration test.

Related issues

N/A

[pkoutsovasilis]

The fips related failures should be resolved by this PR

[elasticmachine]

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

[swiatekm]

Looks good to me at first glance. I checked this out and tried locally doing some of the things it changes, like updating the otel core version, and it all worked correctly.

I do think we should change the edot/pkg package name, but I'm not going to block this PR on it. Once CI passes, I'll approve it.

[v1v]

LGTM - I only reviewed the files in the folder .ci

[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 isolation/move_edot_in_a_separate_package upstream/isolation/move_edot_in_a_separate_package git merge upstream/main git push upstream isolation/move_edot_in_a_separate_package 

[elasticmachine]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: bbfdb43

Failed CI Steps

• Win2025:sudo:fleet
• Win2025:sudo:fleet

History

• 💔 Build #29961 failed 7d9ae63
• 💔 Build #29729 failed b93684f
• 💔 Build #29705 failed c69eb19
• 💔 Build #29700 failed 6cdf425
• 💔 Build #29691 failed df1b5d2

cc @pkoutsovasilis

[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 isolation/move_edot_in_a_separate_package upstream/isolation/move_edot_in_a_separate_package git merge upstream/main git push upstream isolation/move_edot_in_a_separate_package