make input validation, upload logic in build workflows stricter

[jameslamb]

Replaces #334

Contributes to https://github.com/rapidsai/build-infra/issues/237

Makes the following changes in the wheels-build workflow:

• removes input wheel-name
• makes input package-name required
• configures actions/upload-artifact to ERROR if no files are found to upload

Notes for Reviewers

Why, and why now?

When the work to transition artifact-handling from downloads.rapids.ai to GitHub Actions artifacts started, this input referring to the name of the project was called wheel-name.

We later decided that package-name was more appropriate, for consistency with other workflows:

shared-workflows/.github/workflows/wheels-publish.yaml

Line 21 in 1ddf097

package-name:

shared-workflows/.github/workflows/conda-cpp-build.yaml

Line 137 in 1ddf097

id: package-name

But by that time, some PRs calling it wheel-name had already been merged downstream. So both names were kept around for a bit.

Now, there are 0 remaining uses of wheel-name across the rapidsai org: https://github.com/search?q=org%3Arapidsai+%22wheel-name%22&type=code

How I tested this

Searched for wheel-name uses across the rapidsai org and found none remaining: https://github.com/search?q=org%3Arapidsai+%22wheel-name%22&type=code

Searched for wheels-build.yaml across the rapidsai org and found that every use of it was also explicitly supplying a value for input package-name:: https://github.com/search?q=org%3Arapidsai+%22wheels-build.yaml%22+AND+NOT+is%3Aarchived&type=code

Except these repos which are not being actively maintained, and which we've agreed not to worry about for this migration:

• https://github.com/rapidsai/cuspatial/blob/c0f92e5b95f21ccc58d187689bb06adb2fd2bc56/.github/workflows/pr.yaml#L155

[jameslamb]

Reference for this: https://github.com/actions/upload-artifact?tab=readme-ov-file#inputs

When actions/upload-artifact does not find any files to upload at {path}, by default it warns but does not error.

I think for our purposes, we want a big loud CI-failing error, as 0 files being found likely points to a misconfiguration. For any purposes where this workflow is run and you don't want to upload artifacts, we already have an opt-out via the upload-artifacts boolean input: #340