github-actions: use GitHub container registry

[v1v]

What

1. The workflow will create the docker images on demand and store in the GitHub container registry
2. Packages are now accessible at https://github.com/elastic/apm-agent-python/pkgs/container/apm-agent-python%2Fapm-agent-python-testing
3. Use the new container images
4. Less verbose docker pull output

Tests

See https://github.com/elastic/apm-agent-python/actions/runs/14772579891/job/41475033985

[v1v]

#15 5.405 Downloading six-1.17.0-py2.py3-none-any.whl (11 kB)
#15 5.435 Building wheels for collected packages: pytest-localserver
#15 5.436   Building wheel for pytest-localserver (setup.py): started
#15 5.623   Building wheel for pytest-localserver (setup.py): finished with status 'error'
#15 5.628   error: subprocess-exited-with-error
#15 5.628   
#15 5.628   × python setup.py bdist_wheel did not run successfully.
#15 5.628   │ exit code: 1
#15 5.628   ╰─> [8 lines of output]
#15 5.628       /usr/local/lib/python3.10/site-packages/setuptools/dist.py:771: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
#15 5.628         warnings.warn(
#15 5.628       usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
#15 5.628          or: setup.py --help [cmd1 cmd2 ...]
#15 5.628          or: setup.py --help-commands
#15 5.628          or: setup.py cmd --help
#15 5.628       
#15 5.628       error: invalid command 'bdist_wheel'
#15 5.628       [end of output]
#15 5.628   
#15 5.628   note: This error originates from a subprocess, and is likely not a problem with pip.
#15 5.628   ERROR: Failed building wheel for pytest-localserver
#15 5.629   Running setup.py clean for pytest-localserver
#15 5.822 Failed to build pytest-localserver

Known issue, I thin something is wrong with wheel, we have seen that in some other projects, see pypa/wheel#662 (comment)

[xrmx]

#15 5.405 Downloading six-1.17.0-py2.py3-none-any.whl (11 kB)
#15 5.435 Building wheels for collected packages: pytest-localserver
#15 5.436   Building wheel for pytest-localserver (setup.py): started
#15 5.623   Building wheel for pytest-localserver (setup.py): finished with status 'error'
#15 5.628   error: subprocess-exited-with-error
#15 5.628   
#15 5.628   × python setup.py bdist_wheel did not run successfully.
#15 5.628   │ exit code: 1
#15 5.628   ╰─> [8 lines of output]
#15 5.628       /usr/local/lib/python3.10/site-packages/setuptools/dist.py:771: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
#15 5.628         warnings.warn(
#15 5.628       usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
#15 5.628          or: setup.py --help [cmd1 cmd2 ...]
#15 5.628          or: setup.py --help-commands
#15 5.628          or: setup.py cmd --help
#15 5.628       
#15 5.628       error: invalid command 'bdist_wheel'
#15 5.628       [end of output]
#15 5.628   
#15 5.628   note: This error originates from a subprocess, and is likely not a problem with pip.
#15 5.628   ERROR: Failed building wheel for pytest-localserver
#15 5.629   Running setup.py clean for pytest-localserver
#15 5.822 Failed to build pytest-localserver

Known issue, I thin something is wrong with wheel, we have seen that in some other projects, see pypa/wheel#662 (comment)

This was a setuptools version that removed support for description-file after years of deprecations but a new one has been released with the removal reverted. Let me check if I can bump pytest-localserver to something newer than 3 years old.

[xrmx]

Bumped pytest-localserver to a version that should have proper metadata.

[xrmx]

@v1v silly quesiton: will I be able to run this on a branch? I need the image built from the branch adding 3.13 to the matrix in order to have tests for that PR pass.

[v1v]

@v1v silly quesiton: will I be able to run this on a branch? I need the image built from the branch adding 3.13 to the matrix in order to have tests for that PR pass.

Yes, workflow_dispatch: ~ is the way, then, once this PR is merged, you will be able to run on any branch.

---

Let me create a test branch with these changes to validate recent changes

https://github.com/elastic/apm-agent-python/actions/runs/14377179793/job/40312254554 is now running

[xrmx]

Thanks a lot @v1v !