Use CUDA 11.0 migrator

[jakirkham]

Instead of adding a conda_build_config.yaml to affect the manual migration of nvcc, simply add the same CUDA 11.0 migrator as used on other feedstocks. The end result is the same, but it allows this feedstock to match others a bit more closely and simplify things here

Checklist

• [x] 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)
• [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.

xref: https://github.com/conda-forge/nvcc-feedstock/pull/43 xref: https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/794

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

[jakirkham]

@conda-forge-admin, please re-render.

[github-actions[bot]]

Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do.

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