use rapids-build-backend for cugraph-gnn and cugraph-pyg

[jameslamb]

Description

The cugraph-gnn and cugraph-pyg packgaes currently use setuptools as their build backends.

cugraph-gnn/python/cugraph-dgl/pyproject.toml

Line 9 in 666d114

build-backend = "setuptools.build_meta"

cugraph-gnn/python/cugraph-pyg/pyproject.toml

Lines 3 to 8 in 666d114

	[build-system]
	requires = [
	"setuptools>=61.0.0",
	"wheel",
	] # This list was generated by `rapids-dependency-file-generator`. To make changes, edit ../../dependencies.yaml and run `rapids-dependency-file-generator`.

They should use `rapids-build-backend.

Benefits of this work

Would make these projects' build systems consistent with the rest of RAPIDS.

Would reduce the need for complexity like this in build scripts:

cugraph-gnn/ci/build_wheel.sh

Lines 28 to 43 in 666d114

	sed -i "s/name = \"${package_name}\"/name = \"${package_name}${PACKAGE_CUDA_SUFFIX}\"/g" ${pyproject_file}
	echo "${version}" > VERSION
	sed -i "/^__git_commit__ / s/= .*/= \"${git_commit}\"/g" ${version_file}
	# For nightlies we want to ensure that we're pulling in alphas as well. The
	# easiest way to do so is to augment the spec with a constraint containing a
	# min alpha version that doesn't affect the version bounds but does allow usage
	# of alpha versions for that dependency without --pre
	alpha_spec=''
	if ! rapids-is-release-build; then
	alpha_spec=',>=0.0.0a0'
	fi
	for dep in rmm cudf cugraph raft-dask pylibcugraph pylibcugraphops pylibwholegraph pylibraft ucx-py; do
	sed -r -i "s/${dep}==(.*)\"/${dep}${PACKAGE_CUDA_SUFFIX}==\1${alpha_spec}\"/g" ${pyproject_file}
	done

Acceptance Criteria

• cugraph-gnn and cugrpah-pyg use rapids-build-backend as their build backend
• .pre-commit-config.yaml includes the verify-alpha-spec hook
  • example: Use verify-alpha-spec hook cudf#16144

Approach

Follow the work in these examples:

• cugraph changes: Use rapids-build-backend cugraph#4393
• setuptools example: use rapids-build-backend dask-cuda#1343

And other things described in rapidsai/build-planning#31.

Notes

N/A