Increase SIMD levels

[AntoinePrv]

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.

In arrow, SIMD_LEVEL=NONE is not a good baseline.
Since sse-4.2 and neon are not included in the dynamic dispatch, the risk is to not have any acceleration at runtime for the user.
The current efforts in arrow C++ is to enable more dynamic dispatch, reducing the need for making micro-arch builds variant in this feedstock.

• Increase SIMD_LEVEL to default
  • x86-64 -> sse-4.2
  • arm64 -> neon
  • powerpc -> None
• Set runtime SIMD (dynamic dispatch) to max:
  • x86-64 -> [avx2, avx512]
  • arm64 -> possiblly sves in future releases
  • powerpc -> None

[AntoinePrv]

CC @pitrou @h-vetinari

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

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/18923227704. Examine the logs at this URL for more detail.}

[pitrou]

+1 assuming CI passes

[h-vetinari]

Fine by me as well - thanks for this!. If this passes here, I'll test this once more with the python bindings + tests on top (c.f. #1664); that gives a more complete picture IMO, and should reduce the chance of any problems slipping through unnoticed.

[raulcd]

Thanks for doing this @AntoinePrv !

[h-vetinari]

Tests in #1664 look good! :)

Thanks for this, glad to see the situation improved on this!

[conda-forge-admin]

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!