Add cuGraph devcontainers

[trxcllnt]

Description

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

It also adds an optional job to the pr.yaml to build the cuGraph 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 cugraph/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 cuGraph components:

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

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

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

• The C++ build script is a small wrapper around cmake -S ~/cugraph/cpp -B ~/cugraph/cpp/build and cmake --build ~/cugraph/cpp/build
• The Python build script is a small wrapper around pip install --editable ~/cugraph/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 ~/cugraph/cpp -B ~/cugraph/cpp/build
$ CMAKE_ARGS="-Dcugraph_ROOT=~/cugraph/cpp/build" \ # <-- this argument is automatic
  pip install -e ~/cugraph/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.

[trxcllnt]

/ok to test

[trxcllnt]

/ok to test

[trxcllnt]

/ok to test

[trxcllnt]

/ok to test

[trxcllnt]

/ok to test

[trxcllnt]

/ok to test

[trxcllnt]

/ok to test

[trxcllnt]

/ok to test

[trxcllnt]

/ok to test

[rlratzel]

Hi @trxcllnt - I vaguely remember someone mentioning that these images could be built outside of VSCode and the corresponding containers can be used by non-VSCode users. Is that correct, and if so, are there instructions on how to do that?

I still have not installed VSCode yet and did not see how to try these changes in my dev environment.

[trxcllnt]

@rlratzel yes, you can use the devcontainers CLI

[trxcllnt]

/ok to test

[BradReesWork]

/merge