[jsonfusion] Update to 1.1.1

[Aleks Tuchkov (tucher)]

Updates the jsonfusion port to 1.1.1, which also addresses the review feedback on the earlier revision.

Review fixes

• MSVC: upstream supports only GCC 14+ / Clang 20+, so added "supports": "!windows" (the __attribute__((noinline)) etc. do not compile with MSVC).
• yyjson.hpp undeclared dependency: the optional backend headers are now #if __has_include(<...>)-guarded upstream (v1.1.1), so they are self-contained — installing/including them no longer requires the backend to be present; they compile to nothing without it. A yyjson feature pulls the yyjson dependency to activate JsonFusion/yyjson.hpp.
• yaml.hpp includes nonexistent rapidyaml.hpp: same __has_include guard, so the installed header is safe (no-ops without rapidyaml). It is intentionally left unfeatured: the vcpkg ryml port ships a different include layout (<ryml/ryml.hpp>), so it can't satisfy this header cleanly.

Validation (arm64-osx)

• format-manifest — no changes.
• ./vcpkg install jsonfusion — SHA512 verified for v1.1.1; installed headers (including the guarded yaml.hpp / yyjson.hpp) compile standalone with no backend deps present.
• ./vcpkg install jsonfusion[yyjson] — pulls yyjson@0.12.0; JsonFusion/yyjson.hpp compiles against it.

Header-only; boost-pfr dependency unchanged.

• Changes comply with the maintainer guide.
• SHA512s are updated for each downloaded file.
• The version database is updated (x-add-version).
• The installed package builds and can be used.

[Billy O'Neal (BillyONeal)]

GPT 5.6 reports:

Version 1.1.0 installs JsonFusion/yaml.hpp, which includes nonexistent rapidyaml.hpp.
The port advertises default MSVC configurations despite upstream supporting only GCC 14+ and Clang 20+. MSVC compilation fails on constructs such as __attribute__((noinline)).
The installed JsonFusion/yyjson.hpp requires undeclared yyjson.

[Billy O'Neal (BillyONeal)]

Unfortunately __has_include (as suggested in tucher/JsonFusion@1fda63a ) makes it an uncontrolled dependency; we need to patch the __has_include to be always false if we aren't providing the dependency. See https://learn.microsoft.com/vcpkg/contributing/maintainer-guide#when-defining-features-explicitly-control-dependencies

On the other hand it seems like a better fix would be to actually use/provide ryml? https://github.com/biojppm/rapidyaml/blob/master/src/ryml.hpp is named ryml.hpp not rapidyaml.hpp

[Aleks Tuchkov (tucher)]

Thanks — fixed in the latest push.

Controlled dependencies: the portfile now rewrites the __has_include guards to fixed values, so the optional backends are gated by this port's features rather than by whatever is on the include path:

• yaml.hpp → #if 0 (rapidyaml not provided by this port)
• yyjson.hpp → #if 1 with the yyjson feature, #if 0 without

No __has_include remains in those two headers. Validated locally: install jsonfusion and install jsonfusion[yyjson] both build and compile.

On ryml: the version in the vcpkg ryml port isn't the same rapidyaml version JsonFusion currently uses, so it isn't a drop-in. I've left the YAML backend disabled here for now; a proper [yaml] feature can be a follow-up.