Upgrade Core and Blaze

[jviotti]

Signed-off-by: Juan Cruz Viotti jv@jviotti.com

[cubic-dev-ai]

No issues found across 134 files

_{Re-trigger cubic}

[augmentcode]

🤖 Augment PR Summary

Summary: This PR upgrades the vendored sourcemeta/core and sourcemeta/blaze dependencies and migrates JSONBinPack’s test suite away from GoogleTest.

Changes:

• Bumps Core and Blaze revisions in DEPENDENCIES.
• Removes Core’s bundled GoogleTest sources from vendor/core/vendor/googletest (large deletion).
• Updates cmake/FindCore.cmake to stop configuring Core’s GoogleTest-related knobs.
• Introduces/uses Core’s minimal test framework (<sourcemeta/core/test.h>) and its TEST(...)/EXPECT_* macros.
• Switches unit-test CMake wiring from sourcemeta_googletest to sourcemeta_test for compiler/runtime suites.
• Rewrites former EXPECT_THROW-style checks into explicit try/catch blocks with FAIL() and additional assertions.
• Applies the test harness migration consistently across compiler and runtime test sources.

Technical Notes: Test executables now rely on sourcemeta::core::test_main for the default entry point and emit TAP-style output via Core’s runner.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

vendor/core/src/lang/test/CMakeLists.txt:11: sourcemeta_core_test uses sourcemeta::core::Options and sourcemeta::core::stacktrace_on_crash(), but both dependencies are linked as PRIVATE here; in static builds this can leave downstream test executables (that only link sourcemeta::core::test) with unresolved symbols. Can we confirm these dependencies are propagated to consumers (or otherwise guaranteed on the final link line)?

Severity: high

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}