[8.19] (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/8.19/pr-11724
Your branch is up to date with 'origin/8.19'.

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)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   dev-tools/packaging/testing/package_test.go
	both modified:   go.mod
	both modified:   go.sum

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 Succeeded

• Buildkite Build
• Commit: 8c251c6

History

• 💔 Build #34025 failed a844e7d

cc @swiatekm