[libmysql] upgrade to 8.0.32

[kotori2]

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

[kotori2]

I'm wondering... Does the dirname hack in mysql_config really works?

ldata='`dirname $0`/../../data'
execdir='`dirname $0`/../../bin'
bindir='`dirname $0`/../../bin'

Update:
I really don't think it's working... Gonna fix this soon.

 ./mysql_config
Usage: ./mysql_config [OPTIONS]
Compiler: AppleClang 14.0.3.14030022
Options:
        --cflags         [-I./../../include ]
        --cxxflags       [-I./../../include ]
        --include        [-I./../../include]
        --libs           [-L`dirname $0`/../../lib -l -l$<$<NOT:$<CONFIG:DEBUG>>:./../../../../installed/arm64-osx/lib/libz.a> -l$<$<CONFIG:DEBUG>:./../../../../installed/arm64-osx/debug/lib/libz.a> -lOpenSSL::SSL -lOpenSSL::Crypto -lresolv]
        --libs_r         [-L`dirname $0`/../../lib -l -l$<$<NOT:$<CONFIG:DEBUG>>:./../../../../installed/arm64-osx/lib/libz.a> -l$<$<CONFIG:DEBUG>:./../../../../installed/arm64-osx/debug/lib/libz.a> -lOpenSSL::SSL -lOpenSSL::Crypto -lresolv]
        --plugindir      [`dirname $0`/../../lib/plugin]
        --socket         [/tmp/mysql.sock]
        --port           [0]
        --version        [8.0.32]
        --variable=VAR   VAR is one of:
                pkgincludedir [./../../include]
                pkglibdir     [`dirname $0`/../../lib]
                plugindir     [`dirname $0`/../../lib/plugin]

[kotori2]

This PR is ready for review.

[BillyONeal]

This does not seem correct; it's assuming that the caller is going to respect CMake generator expressions, but that's not the intended audience of this thing. If MySQL just wanted cmake to work, they'd be publishing cmake configs, not random bash scripts intended to be used like pkgconfig.

If there's no way to express the difference between release and debug here I think it would be acceptable to just pick release since that seems to be what's expected from pkgconfig-like callers?

[BillyONeal]

Oh wait, I'm an idiot, you're removing those :sigh:

[BillyONeal]

Thanks for the update!