[9.1] (backport #11120) Point beatsauth extension to beats repo

[mergify]

What does this PR do?

This PR now points beatsauthextension component on beats repo.

Why is it important?

beatsauthextension is now moved from elastic/opentelemetry-collector-components to beats repo.

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

Related issues

• ---

  This is an automatic backport of pull request Point beatsauth extension to beats repo #11120 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of e284aff has failed:

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

You are currently cherry-picking commit e284aff84.
  (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)

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   NOTICE-fips.txt
	both modified:   NOTICE.txt
	both modified:   go.mod
	both modified:   go.sum
	deleted by us:   internal/edot/go.mod
	deleted by us:   internal/edot/go.sum
	both modified:   internal/pkg/otel/README.md
	both modified:   internal/pkg/otel/components.go

no changes added to commit (use "git add" and/or "git commit -a")

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 Failed

• Buildkite Build
• Commit: decfbfa

Failed CI Steps

• check-ci
• 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
• :junit: Junit annotate
• 📦 amd64: zip,tar.gz,rpm,deb
• 📦 amd64: zip,tar.gz,rpm,deb
• 📦 amd64: FIPS tar.gz
• 📦 amd64: FIPS tar.gz
• 📦 arm64: zip,tar.gz
• 📦 arm64: zip,tar.gz
• 📦 arm64: FIPS tar.gz
• 📦 arm64: FIPS tar.gz
• 📦 amd64: Containers
• 📦 arm64: Containers
• 📦 amd64: FIPS Containers
• 📦 arm64: FIPS Containers
• Aggregate test reports
• ESS FIPS stack cleanup
• Aggregate test reports

History

• 💔 Build #30221 failed 2ee67dc

cc @khushijain21

[pierrehilbert]

Hey @khushijain21
Could you please fix the conflicts?

[khushijain21]

Requires elastic/beats#47607