Update pin for jpeg

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update the pin for jpeg. The current pinned version is 9, the latest available version is 10 and the max pin pattern is x. This migration will impact 5 feedstocks.

Checklist:

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

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

@conda-forge-admin please ping jpeg

_{This PR was generated by https://github.com/regro/cf-scripts/actions/runs/21342083368 - 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/jpeg 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.

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

For recipe/meta.yaml:

• ℹ️ 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/21342828235. Examine the logs at this URL for more detail.}

[h-vetinari]

So conda-forge/jpeg-feedstock#41 was merged as the first change on that feedstock since almost 2 years. Given conda-forge/jpeg-feedstock#40, I wonder if we want to still migrate this? CC @hmaarrfk

On the other hand, migrating whatever remaining 5 consumers remain (and aren't dead feedstocks anyway) wouldn't be too much of a burden either.

[hmaarrfk]

No. I think we want to abandon jpeg.

I think it will hurt the solver.