Add libcusolver, libcusparse, and libnvjitlink recipes

[leofang]

Part of #21382. Merge after #21901.

Please see the new commits added after commit 93834b6. Discussions are pending.

cc: @jakirkham @adibbley

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 wanted to let you know that I linted all conda-recipes in your PR (recipes/libcusolver) and found some lint.

Here's what I've got...

For recipes/libcusolver:

• The recipe must have some tests.

[conda-forge-webservices]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipes/libcusolver, recipes/libnvjitlink) and found some lint.

Here's what I've got...

For recipes/libcusolver:

• The recipe must have some tests.

[leofang]

@jakirkham @adibbley btw as discussed I am adding libnvjitlink to the same PR

[conda-forge-webservices]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipes/libcusolver, recipes/libnvjitlink) and found some lint.

Here's what I've got...

For recipes/libcusolver:

• The outputs section contained an unexpected subsection name. tests is not a valid subsection name.
• The outputs section contained an unexpected subsection name. tests is not a valid subsection name.

For recipes/libcusolver:

• It looks like the 'libcusolver-dev' output doesn't have any tests.
• It looks like the 'libcusolver-static' output doesn't have any tests.

[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/libcusolver, recipes/libnvjitlink) and found it was in an excellent condition.

[leofang]

@jakirkham @adibbley I can do cusparse in this PR since it requires nvJitLink, but we better get cublas in first

[jakirkham]

Sounds good. Let's go ahead and add libcusparse here then

[bdice]

A few minor tweaks are needed for missing arm-variant constraints, then I can approve. Otherwise LGTM! I verified that all the upstream contents are making it into the downstream packages.

[conda-forge-webservices]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipes/libcusolver, recipes/libcusparse, recipes/libnvjitlink) and found some lint.

Here's what I've got...

For recipes/libcusparse:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [92, 132]

[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/libcusolver, recipes/libcusparse, recipes/libnvjitlink) and found it was in an excellent condition.

[leofang]

@jakirkham @adibbley @bdice @kkraus14 @robertmaynard This is ready.

All comments are addressed/resolved. Let's merge?

[jakirkham]

Thanks all! 🙏

Let's follow up on anything else on the feedstocks