Description

This PR adds some devcontainers to help simplify building the cuML C++ and Python libraries.

It also adds an optional job to the pr.yaml to build the cuML libs in each devcontainer, so the build caches are populated for devs by CI.

A devcontainer can be launched by clicking the "Reopen in Container" button that VSCode shows when opening the repo (or by using the "Rebuild and Reopen in Container" command from the command palette):

Clicking this button will cause VSCode to prompt the user to select one of these devcontainer variants:

On startup, the devcontainer creates or updates the conda/pip environment using cuml/dependencies.yaml. The envs/package caches are cached on the host via volume mounts, which are described in more detail in .devcontainer/README.md.

The container includes convenience functions to clean, configure, and build the various cuML components:

$ clean-cuml-cpp # only cleans the C++ build dir
$ clean-cuml-python # only cleans the Python build dir
$ clean-cuml # cleans both C++ and Python build dirs

$ configure-cuml-cpp # only configures cuml C++ lib

$ build-cuml-cpp # only builds cuml C++ lib
$ build-cuml-python # only builds cuml Python lib
$ build-cuml # builds both C++ and Python libs

• The C++ build script is a small wrapper around cmake -S ~/cuml/cpp -B ~/cuml/cpp/build and cmake --build ~/cuml/cpp/build
• The Python build script is a small wrapper around pip install --editable ~/cuml/cpp

Unlike build.sh, these convenience scripts don't install the libraries after building them. Instead, they automatically inject the correct arguments to build the C++ libraries from source and use their build dirs as package roots:

$ cmake -S ~/cuml/cpp -B ~/cuml/cpp/build
$ CMAKE_ARGS="-Dcuml_ROOT=~/cuml/cpp/build" \ # <-- this argument is automatic
  pip install -e ~/cuml/cpp

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.