[skip-gpuci] Add dependencies.yaml for rapids-dependency-file-generator

[ChuckHastings]

First cut at dependencies.yaml.

We could certainly decompose this more, but wanted to get something out there quickly.

[bdice]

Thanks @ChuckHastings! I have some preliminary comments.

[bdice]

We'll need to split this by arch, since ARM doesn't use the same package name (it uses nvcc_linux-aarch64). See example here from cudf: https://github.com/rapidsai/cudf/blob/2048829ec66af1ceb7a9801702417d12ef13c77a/dependencies.yaml#L83-L94

[bdice]

I think clang/clang-tools can be dropped unless you know a reason why not. Historically these were used only to provide clang-format, as I understand it, and we've been removing these packages from other repos as we migrate to dependencies.yaml. It's possible that some repos (cuML) wish to use clang-tools for running clang-tidy but I don't think that applies to cuGraph.

[ChuckHastings]

I'm OK with removing things. If we remove these from here, how does the C++ code formatting work? Is there some other mechanism we are using?

[bdice]

Many other RAPIDS repos have migrated to using pre-commit as a single source of truth for CI style checks. I will file a PR to update cugraph to match, since that's something we've been doing as part of the GitHub Actions migrations.

For clang-format specifically, switching to pre-commit lets us eliminate this section:

cugraph/ci/checks/style.sh

Lines 33 to 36 in efcf6a8

	# Run clang-format and check for a consistent code format
	CLANG_FORMAT=`python cpp/scripts/run-clang-format.py 2>&1`
	CLANG_FORMAT_RETVAL=$?
	ERRORCODE=$((ERRORCODE | ${CLANG_FORMAT_RETVAL}))

as well as the entire run-clang-format.py file in favor of a single hook definition like this example from cudf.

Then the style check script can also be simplified from ~79 lines to ~23 lines, like cudf.

[bdice]

Where do we depend on boost?

[ChuckHastings]

Looks like we used to depend on boost (circa version 0.6) but we may have eliminated that dependency. I'm testing without it now.

[ChuckHastings]

Removing boost

[bdice]

Let's sort the contents of all packages: lists alphabetically.

[bdice]

Let's use a separate dependency list for Python versions. See cudf example: https://github.com/rapidsai/cudf/blob/2048829ec66af1ceb7a9801702417d12ef13c77a/dependencies.yaml#L190-L204

[ChuckHastings]

@bdice - addressed your comments, ready for more feedback.
@rlratzel - suggestions/thoughts? We talked about some other changes.

[bdice]

Thanks @ChuckHastings! This PR looks good enough to merge. We may have some additional tweaks as we work through GitHub Actions migrations, but this is a great starting point. Much appreciated!

[ajschmidt8]

@ChuckHastings, I pushed some updates here. Let me know if you have any questions. It's mostly just some cleanup, but I also deleted the manually managed conda/environment files and replaced them with a file generated from dependencies.yaml. I only added the CUDA 11.5 variant and removed the old variants. That seems to be the convention we've gone with for other repositories.

Additionally I added a GitHub Action workflow to ensure that the generated files and source dependencies.yaml file stay in sync. This will be an optional GH check for now, but it will be required once we merge the subsequent GH Actions PR for cugraph.