rebuild with Jpeg not turbo

[hmaarrfk]

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.

[conda-forge-webservices]

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.

[h-vetinari]

I'm fine with going back to vanilla jpeg until we have a better solution, but I'd like to have @ocefpaf's input here as well (since he chose to merge libjpeg-turbo intentionally)

[ocefpaf]

I'm fine with going back to vanilla jpeg until we have a better solution, but I'd like to have @ocefpaf's input here as well (since he chose to merge libjpeg-turbo intentionally)

Indeed. I kind of wanted to force our hand to move to turbo. But, to be honest, I won't have time until March to do that is required (proper migration, etc). TL;DR I'm OK reverting and re-visiting this when I have some free time.

[hmaarrfk]

Ok, lets hear the plan out, but I don't think this is the right way to go about it with only a single PR.

i'm sadly reminding of my previous attempt, almost 3 years ago. conda-forge/conda-forge-pinning-feedstock#378