[feature request] Add the ability to build CppInterOp and its downstream projects in a container

[mcbarton]

Description of new feature

I will begin work soon to add the ability to build CppInterOp and its downstream projects inside a container. This issue is more to detail my initial plan

• Add a python script which can used to build CppInterOp and its downstream projects for all platforms where they support said platform (linux, macos, windows and emscripten)
• Add a minimal docker file which simply calls the python script with the correct options, exposing the port needed so that CppInterOp and its downstream projects can be experienced in a browser outside the container
• Add a minimal apptainer file which simply calls the python script with the correct options, exposing the port needed so that CppInterOp and its downstream projects can be experienced in a browser outside the container (apptainer is to cover hpc systems where docker is not available due to security issues)
• Updated the docker and apptainer files to expose a users gpu to the container (if the user has one)

Steps for after this work is done

• Build the docker images locally, and get them uploaded docker hub, so users in future can just download the docker image, and run it locally to experience CppInterOp and its downstream projects

[mcbarton]

@vgvassilev Before I start working on this issue for CppInterOp, I need to know whether your ok with the container files being part of the CppInterOp repo, or would you like it somewhere else. I ask since adding container files to xeus-cpps repo has got push back from Quant Stack developers here compiler-research/xeus-cpp#403

I personally think its good to have it as part of the repo, since we can have binder previews of each repos main + PR previews (I also detail other advantages in the xeus-cpp issue).

If like the Quant Stack developers you also think these container files should be developed outside the repo, point me to where I should create and I will work on it there