feat: add rapids-artifact-name

[gforsyth]

This is part of rapidsai/build-planning#270

It adds a new tool rapids-artifact-name that handles naming more consistently.

The arguments are:

rapids-artifact-name package_type package_name repo --cuda [version] --py [version] --stable --pure

--stable, --py [version], and --pure are mutually exclusive and are only available when naming python artifacts.

> rapids-artifact-name conda_cpp librmm rmm --cuda 12.9
rmm_conda_cpp_librmm_amd64_cu12

> rapids-artifact-name wheel_cpp librmm rmm --cuda 12.9
rmm_wheel_cpp_librmm_amd64_cu12

> rapids-artifact-name conda_python pylibcudf cudf --cuda 13.1 --stable
cudf_conda_python_pylibcudf_amd64_abi3_cu13

> rapids-artifact-name wheel_python pylibcudf cudf --cuda 13.1 --stable
cudf_wheel_python_pylibcudf_amd64_abi3_cu13

> rapids-artifact-name wheel_python dask-cudf cudf --cuda 13.1 --pure
cudf_wheel_python_dask-cudf_amd64_pure_cu13

> rapids-artifact-name wheel_python dask-cudf cudf --pure
cudf_wheel_python_dask-cudf_amd64_pure

I tested this in rapidsai/rmm#2370 by vendoring the script as written there (along with some related small changes to shared-workflows to allow overriding artifact names in the conda cpp builds)

[AyodeAwe]

Do we have a tracking issue for this work? This is so that the surrounding context behind the effort is easily reachable.

[gforsyth]

Do we have a tracking issue for this work? This is so that the surrounding context behind the effort is easily reachable.

Sorry @AyodeAwe -- I tried to cancel the gh pr create call but it instead created the bare PR - I've updated the description!

[AyodeAwe]

LGTM. Two non-blocking suggestions before merge:

1. README: the "Managing CI artifacts" section lists tools with one-liners (including rapids-package-name). Worth adding rapids-artifact-name so it's discoverable?
2. Mark rapids-package-name as deprecated: build-planning#270 already tracks the migration path. While that's in flight, would help to add a header note to the old script pointing readers to the new one, so we don't pick up new callers on the deprecated tool?

[gforsyth]

• README: the "Managing CI artifacts" section lists tools with one-liners (including rapids-package-name). Worth adding rapids-artifact-name so it's discoverable?

• Mark rapids-package-name as deprecated: build-planning#270 already tracks the migration path. While that's in flight, would help to add a header note to the old script pointing readers to the new one, so we don't pick up new callers on the deprecated tool?

Good suggestions! I've added both of them (I removed the rapids-package-name example from the README to avoid confusion)

[gforsyth]

/merge