Update pin for tbb

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update the pin for tbb. The current pinned version is 2021, the latest available version is 2022 and the max pin pattern is x. This migration will impact 15 feedstocks.

Checklist:

• The new version is a stable supported pin.
• I checked that the ABI changed from 2021 to 2022.

**Please note that if you close this PR we presume that the new pin has been rejected.

@conda-forge-admin please ping tbb
This PR was generated by https://github.com/regro/cf-scripts/actions/runs/11634373072 - please use this URL for debugging.

[conda-forge-webservices]

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

I was asked to ping @conda-forge/tbb and so here I am doing that.

[conda-forge-admin]

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

[h-vetinari]

Let's try to wrap up the libhwloc migration before doing this. We haven't updated tbb in a long time.

[adrianinsaval]

@hmaarrfk conda-forge/smesh-feedstock#98 needs tbb 2022 (and any other occt 7.9 migration) can this be merged too or should I pin it to 2022 in conda_build_config?

[h-vetinari]

Unfortunately, tbb 2022 conflicts with our current MKL constraint (<2025), because mkl 2024 depends on tbb 2021.*

I've been wanting to unblock MKL 2025 for a long time (and newer lapack even longer), but it's currently stuck due to changes in how MKL handles some symbols internally. See conda-forge/intel_repack-feedstock#83 and conda-forge/blas-feedstock#128

[traversaro]

xref related PR on the tbb side:

• Rebuild 2021.13 for libhwloc 2.12.1 tbb-feedstock#143
• Add 2021.13 to abi_migration_branches tbb-feedstock#144

Unfortunately, tbb 2022 conflicts with our current MKL constraint (<2025), because mkl 2024 depends on tbb 2021.*

Just a curiosity, do you have any idea why there is such a pin? At least according to the tbb feedstock metadata, all tbb version after 2021 are ABI compatible (see https://github.com/conda-forge/tbb-feedstock/blob/e7c3fab5cc1de343733640d6fd893b5a81353af2/recipe/meta.yaml#L108-L109, not sure if this is actually realistic to be honest), but indeed if tbb is used in some strange ways in the public headers things can go complex really quick, see for example conda-forge/openusd-feedstock#9 .

[h-vetinari]

Just a curiosity, do you have any idea why there is such a pin? At least according to the tbb feedstock metadata, all tbb version after 2021 are ABI compatible

Intel uses a mix of both semver and calver, so 2022 will not be compatible: conda-forge/intel_repack-feedstock#81

stale

[h-vetinari]

Now that #6666 is in, we can do this. Would have been nice to do this simultaneously with mkl2025, but at least I've added a wait_for_migrators: for now.