Update MKL to 2022.0 build

[haasad]

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.

Update to latest MKL: conda-forge/intel_repack-feedstock#32

@h-vetinari I saw that you're also working on supporting blas 3.9.1 and blas 3.10, but according to conda-forge/intel_repack-feedstock#32 (comment) mkl 2022.0 doesn't yet support them.

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

[haasad]

@conda-forge-admin, please rerender

[h-vetinari]

This will probably need a conda_build_config.yaml with the following content (+ a rerender):

mkl:        # [win]
  - '2021'  # [win]
mkl_devel:  # [win]
  - '2021'  # [win]

This is because the global pinning puts mkl at 2021, and when the unpinned mkl gets added for blas-devel (through the pinning), it conflicts with the rest of the recipe.

Alternatively (and arguably the better solution) is to just parametrize the mkl-version as a jinja-variable and re-use it in the blas-devel output.

[h-vetinari]

This will also need to be rebased & rerendered after #82.

[haasad]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/blas-feedstock/actions/runs/1693832693.

[isuruf]

@conda-forge-admin, rerender