stop uploading packages to downloads.rapids.ai, update to 25.08 workflows

[jameslamb]

Description

Contributes to rapidsai/build-planning#181

• removes all uploads of conda packages and wheels to downloads.rapids.ai
• updates all shared-workflows references to branch-25.08, to pull in changes from Use GitHub Actions artifacts in Anaconda uploads shared-workflows#364

Notes for Reviewers

How I identified changes

Looked for uses of the relevant gha-tools tools, as well as documentation about downloads.rapids.ai, being on the NVIDIA VPN, using S3, etc. like this:

git grep -i -E 's3|upload|downloads\.rapids|vpn'

How I tested this

See "How I tested this" on rapidsai/shared-workflows#364

Checklist

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

[ncclementi]

If we don't upload the wheels, what do we put them now, just push them to pypi or directly or something after building them?

[jameslamb]

They're getting uploaded to the GitHub Actions artifact store.

via this:

https://github.com/rapidsai/shared-workflows/blob/e62a069ab2266fa1508081ffff59869f68a78a33/.github/workflows/wheels-build.yaml#L249-L254

Which gets called because we use it here:

rapids-cli/.github/workflows/pr.yaml

Lines 20 to 21 in 3ec5fc5

	build-wheel:
	uses: rapidsai/shared-workflows/.github/workflows/wheels-build.yaml@branch-25.06

You can see those artifacts at the end of any CI run here, by scrolling down to the "Artifacts" section. For example, from this PR: https://github.com/rapidsai/rapids-cli/actions/runs/15287088447?pr=98

[ncclementi]

Thanks, that makes sense : )

[jameslamb]

Yep no prob! Happy to answer any other question you have, there's a TON of indirection involved here.

[ncclementi]

LGTM 🚀

[ncclementi]

Thanks, that makes sense : )