[fmt] Fix visibility

[xiaozhuai]

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

ld: warning: direct access in function 'fmt::v10::detail::format_error_code(fmt::v10::detail::buffer<char>&, int, fmt::v10::basic_string_view<char>)' from file '/usr/local/vcpkg/installed/x64-osx/lib/libfmt.a(format.cc.o)' to global weak symbol 'decltype(fp.begin()) fmt::v10::detail::parse_format_specs<int, fmt::v10::detail::compile_parse_context<char> >(fmt::v10::detail::compile_parse_context<char>&)' from file '/usr/local/vcpkg/installed/x64-osx/lib/libspdlog.a(spdlog.cpp.o)' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.

When link with spdlog, it shows this warning.

This problem was once reported in #29280 by @marcovc

And this pr fix it.

[BillyONeal]

Has this been reported upstream? /cc @vitaut

[dg0yt]

AFAIU #29280 points also at spdlog.
Is it right fix to generally deactivates fmt's visibility defaults?
And the patch is deactivating input (cache) variables. Is a patch needed at all?

[xiaozhuai]

See fmtlib/fmt#3769 and fmtlib/fmt@f68f452

[xiaozhuai]

@LilyWangLL @BillyONeal

[LilyWangLL]

@xiaozhuai Please fix the CI pipeline error: arrayfire:x64-osx.

CMake Error at CMakeModules/AFconfigure_forge_submodule.cmake:47 (configure_file):
  No such file or directory
Call Stack (most recent call first):
  CMakeLists.txt:115 (include)

[xiaozhuai]

Please fix the CI pipeline error: arrayfire:x64-osx.

@LilyWangLL It seem nothing to do with this PR. See #33540

[LilyWangLL]

Please fix the CI pipeline error: arrayfire:x64-osx.

@LilyWangLL It seem nothing to do with this PR. See #33540

Thanks for your reply, this error should add DISABLE_PARALLEL_CONFIGURE for arrayfire, PR #33540 has added this.