Use new constraints type from DFG

[KyleFromNVIDIA]

As of rapids-dependency-file-generator v1.22.0, a new output type, constraints, is supported, allowing constraints to be separated from requirements. Use this where possible.

For now, be overzealous in turning on constraints wherever requirements is used. If we ever run into issues with constraints having extras, we can deal with it at that time.

Contributes to rapidsai/build-planning#311

[greptile-apps]

Greptile Summary

The PR adopts DFG v1.22.0's dedicated constraints output for wheel CI.

• Adds constraints coverage to requirement-compatible dependency groups.
• Generates torch and wheel-test constraint files using the new output type.
• Updates the pre-commit DFG revision to v1.22.0.

Confidence Score: 5/5

The PR appears safe to merge with no substantive changed-code defect identified.

The generator upgrade, dependency metadata, and CI consumers are updated coherently to use the new constraints output while preserving the existing package pins and pip index options.

Important Files Changed

Filename	Overview
dependencies.yaml	Adds constraints output consistently to dependency groups that already support requirements output.
ci/download-torch-wheels.sh	Generates the torch pin file using the dedicated constraints output before passing it to pip download.
ci/test_wheel_cugraph-pyg.sh	Requests constraints-format dependency output for the cugraph-pyg wheel test environment.
ci/test_wheel_pylibwholegraph.sh	Requests constraints-format dependency output for the pylibwholegraph wheel test environment.
.pre-commit-config.yaml	Updates the dependency-file generator to the release introducing constraints support.

_{Reviews (1): Last reviewed commit: "Use new `constraints` type from DFG" | Re-trigger Greptile}