Generally enable CUDA 12 cross-compilation

[jakirkham]

As CUDA 12 uses standard conda-forge images and ships a CUDA Toolkit enabled for cross-compilation, there is no need to check for CDT_NAME in the CUDA 12 check. Any value conda-forge otherwise supports should also apply to CUDA 12.

CUDA 11 still requires special handling. Though this is not changed here.

---

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[jakirkham]

@conda-forge/core this is ready for review! 😄

[h-vetinari]

This doesn't yet do what you want. That whole branch is under

conda-forge-ci-setup-feedstock/recipe/cross_compile_support.sh

Lines 43 to 45 in 170fdf8

	if [[ "${CUDA_COMPILER_VERSION}" == "11.2" || "${CUDA_COMPILER_VERSION}" == "11.8" ]] && [[ "${CDT_NAME}" == "cos8" || "${CDT_NAME}" == "cos7" ]]; then
	# We use cdt_name=cos7 for rhel8 based nvcc till we figure out
	# a stable cos8 replacement.

which needs adaptation as well e.g. cdt_name in ["conda", "cos7"].

I'd also prefer to fully drop CUDA 11.2 from the setup here. We've dropped it half a year ago, so no need to carry this cruft around anymore IMO.

[h-vetinari]

This comment is then also outdated.

[h-vetinari]

same here

[jakirkham]

Closing as this appears to be addressed by PR: #365