Use devcontainers to simplify kit configuration

devcontainers allow a user to combine a Docker Container with IDE specific settings.

// For format details, see https://aka.ms/devcontainer.json. For config options, see the
// README at: https://github.com/devcontainers/templates/tree/main/src/alpine
{
    "name": "Minimum spec container (arm64)",
    "build": {
        "dockerfile": "../../tests/manual/docker/linux/Dockerfile-gcc-10",
        "options": [
            "--platform=linux/arm64",
            "--build-arg",
            "platform=arm64"
        ]
    },
    "customizations": {
        "vscode": {
            "extensions": [
                "ms-vscode.cmake-tools",
                "theqtcompany.qt"
            ],
            "settings": {
                "qt-core.additionalQtPaths": [
                    "/6.7.0/gcc_arm64/bin/qtpaths"
                ],
            }
        }
    }
}

This can allow a user to prepare a full development environment for his colleagues or customers.

A hardware vendor can create a development container for developers to utilize. A developer will then be able to grab the docker container with the hardware-specific tools, and then from Qt Creator instantiate that container so that the compiler & other tools it contains are available when selecting a kit for a project.

What the hardware vendors see as the largest benefit over their current (manual or scripted) project initiation workflow is that the developer does not need to configure anything or be required to run scripts to do the configuration actions.

User stories / tasks 

TBD

References

OKR 2025/June-Sept: D-4-3