buildbot runner image is incomplete

[xjia1]

The existing list seems incomplete because it's missing git. Need to revise based on https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2204-Readme.md

[xjia1]

https://github.com/nstests/bjtest/actions/runs/6462178590/job/17543436621

2023-10-09T22:39:26.7097534Z In file included from ./boost/python/detail/prefix.hpp:13,
2023-10-09T22:39:26.7098284Z                  from ./boost/python/converter/registrations.hpp:8,
2023-10-09T22:39:26.7098841Z                  from libs/python/src/object/function_doc_signature.cpp:9:
2023-10-09T22:39:26.7099274Z ./boost/python/detail/wrap_python.hpp:57:11: fatal error: pyconfig.h: No such file or directory
2023-10-09T22:39:26.7099653Z    57 | # include <pyconfig.h>
2023-10-09T22:39:26.7099900Z       |           ^~~~~~~~~~~~
2023-10-09T22:39:26.7100148Z compilation terminated.

sudo apt install python3-dev

[xjia1]

This is already fixed in the dimerun image where we use the official runner image packer build scripts to install all dependencies. Not sure if it's applicable to a docker image.

[xjia1]

Need to rethink this because the github image is very large.

[xjia1]

I'd like to see if it is feasible to just use the official runner image from GitHub Actions. Last time I checked it used about 35 GiB of disk space. Not sure about the size after compression.

Somethings we should try:

• Install the GHA runner image as a container image, not VM
• Check the size of the container image and if it's feasible to distribute it via GHCR
• Remove components from the GHA runner image to see if we can reduce the size to a more reasonable value without losing too many features. The target size is mostly dependent on how much disk space we get from the various cloud providers using our recommended minimum configurations