Add cuda-nvdisasm, cuda-nvprof, cuda-nvvp recipes

[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/cuda-nvdisasm, recipes/cuda-nvprof, recipes/cuda-nvvp) and found some lint.

Here's what I've got...

For recipes/cuda-nvprof:

• The top level meta key tests is unexpected
• The recipe must have some tests.

For recipes/cuda-nvvp:

• The top level meta key tests is unexpected
• The recipe must have some 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/cuda-nvdisasm, recipes/cuda-nvprof, recipes/cuda-nvvp) and found it was in an excellent condition.

[bdice]

Looks good to me.

[jakirkham]

Thank you both! 🙏

Let's get these out and follow up on anything else in the feedstock