Add cccl recipe (rename from cuda-cccl-impl).

[bdice]

This PR adds the cccl package, which is a rename of the cuda-cccl-impl package (identical contents for now). Due to some upstream reorganization of the CCCL libraries (thrust, cub, libcudacxx) it now makes sense to make cccl the proper name for this user-facing package, instead of cuda-cccl-impl which sounds like an internal "implementation" package.

This rename has been discussed with stakeholders/maintainers here: conda-forge/cuda-cccl-impl-feedstock#2

This rename is being opened as a new staged recipe in accordance with this guide: https://conda-forge.org/docs/orga/guidelines.html#renaming-packages

For reference, the cuda-cccl-impl package was previously added in #21953.

After this PR is merged, I will follow up with a few downstream recipes to update them.

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-webservices]

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 (recipes/cccl) and found it was in an excellent condition.

[bdice]

@adibbley Can you comment here to indicate you're willing to be listed as a maintainer?

Also cc: @jakirkham @jrhemstad for visibility

[jakirkham]

Thanks Bradley! 🙏

Think we will want to add run_constrained sections to both recipes to prevent clobbering

[jakirkham]

cc @adibbley

[adibbley]

@adibbley Can you comment here to indicate you're willing to be listed as a maintainer?

Yes, thanks!

[bdice]

@adibbley @jakirkham Anything else we need here before requesting a final review/merge?

[jakirkham]

Thanks Bradley! 🙏

Had a few suggestions below

[jakirkham]

Wonder if there is a CMake install approach we can use here in the future

[bdice]

This can be reworked with CCCL 2.2 which releases from the new monorepo. Let’s keep the status quo for now since this is just renaming a package we have already tested/used a bit and trust.

[jakirkham]

Thanks Bradley & Alex! 🙏