General update to trixie with python 3.13 (WIP)

[bjoernt]

Changelog:

• Adding arg GHCR_URL to allow builds to self reference forked repos for testing

• Switch images to Python 3.13 trixie for 2025.1 and up, 2024.1 uses python 3.12 due to cffi global requirements constraint. The nova image is currently locked to python3.12 due to compile errors

• Add matrix build for openstack-venvs to build bookworm and trixie images

• Add Ceph Squid clients to bookworm and trixie ceph-client container matrix builds

  • Update tagging with -- format such as squid-3.12-bookworm

• Skyline builds from os-constraints branches now as rebase to 2025.1 broke 2024.1 release (sqlalchemy version mismatch)

• Rebase glance,cinder,nova containers to layer off ceph-client instead of openstack-venv

• Minor bump of libguestfs to v1.56.2

• Minor bump of ovs to 3.5.2

• Recode blazar to unix file format

[bjoernt]

The builds are expected to fail until the dependent containers are build such as openstack-venv, libvirt etc

[cloudnull]

i think this is a good start, and I like where some of this is going. but I think its too big and impactful. I'd like to start with one or two containers, and then see how it goes? maybe start with something like blazar or zaqar where any initial impact is very low, let us work out the patterns, and bugs, then do a full-scale rollout.

[cloudnull]

we just got the ceph libs building using a private runner, i'm dont think we eant to go back on that now?

[cloudnull]

why are we setting the ghcr_url? i see it in the build args, but what purpose does it serve?

[bjoernt]

This is there to allow containers build to reference multi stage from forked repos, like openstack-venv so you can test and build the entire chain like I had to from a forked repo instead of using hard coded repos

FROM ${GHCR_URL}/openstack-venv:${VENV_TAG} AS dependency_build