[libjpeg-turbo] update to 3.1.4.1

[toge]

• Changes comply with the maintainer guide.
• SHA512s are updated for each updated download.
• The "supports" clause reflects platforms that may be fixed by this new version, or no changes were necessary.
• Any fixed CI baseline and CI feature baseline entries are removed from that file, or no entries needed to be changed.
• All patch files in the port are applied and succeed.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Exactly one version is added in each modified versions file.

https://github.com/libjpeg-turbo/libjpeg-turbo/releases/tag/3.1.4.1

[toge]

REGRESSIONS:
REGRESSION: kf6i18n:x64-windows failed with FILE_CONFLICTS. If expected, add kf6i18n:x64-windows=fail to D:\a\_work\1\s\scripts\azure-pipelines/../ci.baseline.txt.
REGRESSION: kf6itemmodels:x64-windows failed with FILE_CONFLICTS. If expected, add kf6itemmodels:x64-windows=fail to D:\a\_work\1\s\scripts\azure-pipelines/../ci.baseline.txt.
##[error]vcpkg ci testing failed, but no build failure logs were created for this error.

[Neustradamus]

Dear all, @toge, @vicroms,

Thanks for your work and merging!

But I have discovered a problem, for example with this port, it is always old:

• https://vcpkg.io/en/package/libjpeg-turbo.html

Why?

[vicroms]

@Neustradamus

Unfortunately, due to several internal security compliance requirements, we cannot automate the website updates. The source of truth for available versions is this repository; the website is usually a week behind.