[libmodplug] Fix WASM build by pinning C++ standard to 11

[fwcd]

Fixes #37089

The port uses the register storage class specifier which was removed in C++17, pinning the standard to C++11 solves this.

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

[FrankXie05]

Suggested change

	-DCMAKE_CXX_STANDARD=11
	)
	-DCMAKE_CXX_STANDARD=${CXX_STANDARD}
	)
	if(VCPKG_TARGET_ARCHITECTURE STREQUAL "wasm32")
	set(CXX_STANDARD 11)
	endif()

Regarding specifying the c++ version, especially the lower standard approach, I think we should filter it。

[fwcd]

If we do this, I would probably go with VCPKG_TARGET_IS_EMSCRIPTEN, since this is specific to the compiler. Off top of my head, we'd probably also have to move it above the configure.

I'm actually a bit surprised that it builds on all other major platforms as-is though, especially given that Emscripten just runs Clang under the hood. Maybe the major compilers are more lenient when it comes to accepting older C++ standards by default?

[FrankXie05]

Upstream has no special instructions for the C++ standard, so a lower standard may be accepted. ：）

[FrankXie05]

It's better to use VCPKG_TARGET_IS_EMSCRIPTEN.

[FrankXie05]

Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review".
That way, I can be aware that you've responded since you can't modify the tags.