[vcpkg baseline][opencv4] Control intel-mkl dependency

[dg0yt]

Assumed to fix the openimagio:x64-linux CI baseline regression, given the <opencv4 libs> <intel-mkl libs> argument sequence of the failing link step.

(This PR is just to resolve the baseline regression without completely disabling intel-mkl for opencv4, not to ensure that opencv4[mkl] correctly exports link libraries for downstream usage as in openimagio.)

Related: #30570.

• 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
• Any fixed CI baseline entries are removed from that file.
• Any patches that are no longer applied are deleted from the port's directory.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

[BillyONeal]

Sadly I think this is an alternative :(

[BillyONeal]

I don't think this fix is correct. opencv should be listening to what the blas and lapack metaports say in order to determine which blas/lapack to use, and shouldn't really be controlling something that is an alternative like this with the feature mechanism. I'm looking at a fix now.

[BillyONeal]

I think the right fix is to always pass OPENCV_LAPACK_FIND_PACKAGE_ONLY. If someone wants to use mkl, they should overlay the lapack port to do that. What do you think?

[dg0yt]

I cannot check the details soon, but I tend to agree that the mkl feature shouldn't be there.

[BillyONeal]

I cannot check the details soon, but I tend to agree that the mkl feature shouldn't be there.

OK, I validated that that change actually fixes the problem and have submitted a competing proposal here: #30883

[dg0yt]

Replaced by #30883.