Add cuQuantum Python 22.11.0.1 and expand tests

[leofang]

Checklist

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

[conda-forge-linter]

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

[conda-forge-webservices[bot]]

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

[leofang]

Note to future self: we don't need to use pin_compatible here https://github.com/conda-forge/cuquantum-feedstock/blob/6af0091861362a5895927dcaead6756c52e2f9d2/recipe/meta.yaml#L163-L164 is because both MPI packages have done it for us (via run_exports):

• https://github.com/conda-forge/mpich-feedstock/blob/c6c81b3068faa81abf30b7cab8c025e61d8669e9/recipe/meta.yaml#L39-L40
• https://github.com/conda-forge/openmpi-feedstock/blob/3217373754a82a54c3862eefd6dc31534be3cf52/recipe/meta.yaml#L29-L30

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[JeremyWangNVDA]

The version bump LGTM