[9.2] (backport #11724) Use google/go-containerregistry to parse OCI images in packaging tests

[mergify]

What does this PR do?

Uses the google/go-containerregistry package to parse container tarballs in package tests, instead of parsing them manually. The tests now pass for images exported from the containerd image store.

Why is it important?

The current code only handles one container archive format. In particular, it doesn't handle exports from the containerd snapshotter, which docker enables by default for new installations as of v29.0. After the change, both formats are supported. We currently ship our tarballs using the older format, but eventually want to switch to the newer one. This change will also make package tests pass locally for new docker installs.

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

How to test this PR locally

Build a container image with the containerd image store enabled and run package tests via mage testPackages.

Related issues

• Relates Docker builds failing with invalid tar header or EOF errors #11604

---

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

[mergify]

Cherry-pick of 44814ff has failed:

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

You are currently cherry-picking commit 44814ff4e.
  (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:   dev-tools/packaging/testing/package_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.mod
	both modified:   go.sum

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: 1cf17bc

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
• 📦 amd64: zip,tar.gz,rpm,deb
• 📦 amd64: zip,tar.gz,rpm,deb
• 📦 amd64: OTEL_COMPONENT zip,tar.gz,rpm,deb
• 📦 amd64: OTEL_COMPONENT zip,tar.gz,rpm,deb
• 📦 amd64: FIPS tar.gz
• 📦 amd64: FIPS tar.gz
• 📦 arm64: zip,tar.gz
• 📦 arm64: zip,tar.gz
• 📦 arm64: OTEL_COMPONENT zip,tar.gz
• 📦 arm64: OTEL_COMPONENT zip,tar.gz
• 📦 arm64: FIPS tar.gz
• 📦 arm64: FIPS tar.gz
• 📦 amd64: Containers
• 📦 arm64: Containers
• 📦 amd64: FIPS Containers
• 📦 arm64: FIPS Containers
• 📦 amd64: OTEL_COMPONENT Containers
• 📦 arm64: OTEL_COMPONENT Containers
• Aggregate test reports
• ESS FIPS stack cleanup
• Aggregate test reports
• :pipeline: Run elastic-agent-package

History

cc @swiatekm