wheels: add tests similar to 'test-nightly-conda-env'

Description

The test-nightly-conda-env tests have been useful for catching problems like:

• "project {X} hasn't uploaded any new packages in the last {n} days"
• "some dependency conflict(s) prevent the all-of-RAPIDS conda environment for solving to the latest nightlies"

It's possible because a date component is included in version strings for RAPIDS nightly conda packages.

As of https://github.com/rapidsai/shared-workflows/pull/603, nightly wheels will have a date-based version component. Similar tests for wheels should be added here.

Benefits of this work

• catch similar publishing issues, dependency conflicts, etc. for wheels

Acceptance Criteria

• a test-nightly-wheels-env (or similar) CI job exists which checks that all of RAPIDS is installable together from wheels on the platforms we formally support

Approach

Look at the implementation in https://github.com/rapidsai/integration/blob/main/ci/check_conda_nightly_env.py as a starting point.

Notes

N/A

Start by examining the existing test-nightly-conda-env job and ci/check_conda_nightly_env.py. Use that implementation and the supported-platform configuration to determine how the corresponding wheel environment check is organized. Done means a test-nightly-wheels-env (or similar) CI job verifies that all of RAPIDS is installable together from nightly wheels on formally supported platforms.