Modernization Phase 1.1: build-system hygiene (Ninja, CMake 3.28 floor, presets, cmake-file sync)

[ptesavol]

Phase 1.1 of the modernization plan: build-system hygiene with no compiler or dependency changes. Everything here is a prerequisite for the LLVM 22 upgrade (Phase 1.2) and the C++ modules migration (Part 2).

Changes

1. Ninja generator everywhere. install-prerequisities.sh exports CMAKE_GENERATOR=Ninja (current shell + setenvs.sh + CI's GITHUB_ENV) and brew install ninja on macOS (Linux already installed ninja-build). Ninja is faster than Makefiles and is required by CMake's C++ modules support. ⚠️ Devs must run ./clean.sh once after this lands — CMake errors on generator change in an existing build dir (README updated).
2. All test.sh scripts unified from one template: cmake ..; make → generator-agnostic cmake --build build; per-package env vars preserved. Fixes a latent bug: the streamr-utils/streamr-proto-rpc variants dropped ctest's exit code and could never report failure.
3. CMake floor 3.28...4.3 in all 9 CMakeLists (was 3.22). 3.28 = first CMake with stable C++ modules support; ubuntu-24.04's stock cmake is 3.28.3.
4. CMAKE_CXX_STANDARD_REQUIRED ON next to every CMAKE_CXX_STANDARD 26.
5. CMAKE_CXX_SCAN_FOR_MODULES OFF next to every standard setting — see "found during CI" below.
6. Canonical cmake/ dir + sync-cmake-files.sh. Per-package copies of homebrewClang.cmake/monorepoPackage.cmake stay (standalone vcpkg publishing goal) but are generated from canonical files; lint.sh/CI fail if a copy drifts.
7. monorepoPackage.cmake divergence fixed: canonical file appends dep dirs to both CMAKE_PREFIX_PATH and CMAKE_FIND_ROOT_PATH (previously only streamr-logger had the FIND_ROOT_PATH variant — the one that works under cross-compiling toolchains).
8. Root CMakePresets.json (host/ios/android × debug/release). install.sh intentionally untouched this phase.
9. CI diagnostics without log access: lint.sh emits the failing package's output tail as a GitHub ::error:: annotation; test.sh emits failed test names (ctest's LastTestsFailed.log). These show up in the Checks UI and the anonymous annotations API.

Found during CI iteration on this PR

• CMP0155 vs clangd (fixed here): the 3.28 floor auto-enabled scanning of all C++20+ sources for module imports. Under Ninja + GCC, CMake injects -fmodules-ts -fmodule-mapper=... -fdeps-format=p1689r5 into compile_commands.json; gcc accepts them, but clangd rejects them as unknown arguments → lint failed on both Linux legs. Fixed with CMAKE_CXX_SCAN_FOR_MODULES OFF (there are no module sources yet; the modules migration re-enables scanning deliberately). Good news for Part 2: with Clang, scanning happens via a separate clang-scan-deps step and compile commands stay clean, so the lint pipeline survives the modules era once Linux moves to Clang (Phase 1.2).
• Pre-existing on main, NOT from this PR: the Linux test step is red. Both on the PR Modernization Phase 1.0: baseline & repo fixes #20 run and on main's own post-merge run, both Linux legs go install ✓ → lint ✓ → test ✗. The failed test names are now visible via the new test.sh annotation. Recommend treating the test failures as a separate workstream; this PR's gate is therefore: install + lint green on both Linux legs, test failing identically to main.

Expected CI status

• ubuntu-24.04 / linux-arm64: install ✓, lint ✓ (after the fix), test ✗ (pre-existing, same as main).
• macos-13/14: expected RED until Phase 1.2 (dead llvm@17, unchanged).
• iOS/Android: skipped (keyword-gated).

Next

Phase 1.2: compiler upgrade — Homebrew LLVM 17 → latest, Linux gcc-14 → clang + libc++, keg-only LLVM handling via LLVM_PREFIX, with the iOS runtime-libc++ compatibility gate (device test) you specified.

🤖 Generated with Claude Code

[ptesavol]

CI outcome on the final commit (523074f), matching the expectations in the description:

Leg	install	lint	test
ubuntu-24.04	✅	✅	❌ (pre-existing)
linux-arm64-runner	✅	✅	❌ (pre-existing)
macos-13/14	❌ expected until Phase 1.2	—	—

The test failures are identical to main and are exactly three tests on both legs (now visible via the new annotations): ts-integration-test, ts-end-to-end-test, ts-multiple-messages-test — i.e. only the TypeScript-interop integration tests; all C++ tests pass. Suggest handling those as a separate workstream.

Ready for review.

🤖 Generated with Claude Code