Add CUDA 11.3/11.4/11.5

[ajschmidt8]

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.

Similar to #69, except it also adds 11.5 and has no merge conflicts 🙂

[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.

[leofang]

Hi @ajschmidt8, since you're touching this feedstock, could you change all cos8 occurrences to cos7 in recipe/conda_build_config.yaml and rerender please? It was a mistake we made earlier. The only impact of this change is on the package hash string, but since you're bumping the build number anyway it doesn't matter.

[leofang]

Hi @isuruf, looks like the CUDA 11.5 docker images are currently not visible? Could you check for us please?

[ajschmidt8]

For reference, I have a PR to add 11.5 images below. This PR will likely continue to fail until it's merged. However, I think that PR is dependent on the 11.5 variants of the nvidia/cuda DockerHub images being published

• Add CUDA 11.5 variants to CI axis docker-images#198
• https://hub.docker.com/r/nvidia/cuda

[leofang]

Thanks AJ, I mistakenly thought the 11.5 image has been added, my bad!

[leofang]

btw for Windows, we need this PR conda-forge/conda-forge-ci-setup-feedstock#154 to be merged (and add 11.5 support on top of that).

[jaimergp]

Fixed conflicts and added 11.5 there!

[kkraus14]

We may also be blocked by conda-forge/docker-images#198 here

[leofang]

@conda-forge-admin, please rerender

[kkraus14]

Thanks @ajschmidt8!