Development Host Toolchain Containerization

For Qt DC, we need macOS host support (which is however provided natively now). Additionally to this, we can see in horizon two major changes to earlier days: (1) We will need to support all current hosts on both Intel and ARM based hosts duplicating hosts support, and (2) simultaneously we need to support more embedded target OS+HW combinations (Yocto + RTOS + AAOS + Ubuntu) than before (mainly Yocto + RTOS). Old style doing host specific cross compilation toolchains is not sustainable to keep up with the changing world.
Out of scope of this Epic but part of future: We also have developer teams that would like to orchestrate their targets management so that a project lead can centrally manage the team targets qualities, and sometimes also move compilation and packaging outside of the host machine.
Out of scope for this Epic but related: Simultaneously, we have customers and partners who want to create target systems where the target application is running in a container instead of directly on target OS. This part is partially overlapping with the business need defined above but out of scope for the main purpose of this Epic.

Able to deploy from Containerised (Docker) toolchain to embedded HW (using native image as today as opposed to running a container on embedded). At least the following uses cases are needed:
-Develop on Mac on ARM or x86_64 and deploy onto Yocto on ARM or x86_64
-Develop on WIndows on x86_64 and deploy on Yocto on ARM or x86_64
-Develop on Linux on ARM or x86_64 and deploy on Yocto on ARM or x86_64

We want to use the same x86_64 linux toolchain container in all hosts, so also in M1 macOS.
Docker Desktop for Apple silicon also supports multi-platform images,
which allows you to build and run images for both x86 and ARM
architectures without having to set up a complex cross-compilation
development environment.