DR-008 Option 4: two-stage test-execution workflow (PR 2 of 2)

[Subramanian-K812]

DR-008 Option 4: two-stage test-execution workflow (PR 2 of 2)

Closes #264. This is the second of two PRs. It is stacked on PR 1
(Subramanian-K812_resolve_override_mechanism, "resolved-dependency resolve + override
mechanism") — please review/merge that one first. Until PR 1 merges, this PR's base branch
is the PR-1 branch, so the diff shown here is only the test-execution delta.

What this PR does

Rewires the quality workflow to the DR-008 Option 4 flow, using the resolve + override
mechanism added in PR 1:

1. Stage 1 — integration: builds the platform, runs Feature Integration Tests, and
   exports the resolved dependency set as the stage1-resolved-deps artifact
   (resolved_versions.json).
2. prepare_matrix: derives the Stage-2 module list dynamically from
   known_good.json (target_sw) — never hardcoded.
3. Stage 2 — per module: checks the module out at its known_good commit, overrides
   its MODULE.bazel with the Stage-1 resolved set (PR 1's mechanism), and runs the
   module's own unit tests + coverage as the Bazel root (//...).
4. aggregate: consolidates Stage 1 + Stage 2 into one quality report (and the
   release-tag test-report ZIP).

Files

Workflow & runners

• .github/workflows/test_and_docs.yml — two-stage restructure (+ parallel docs build)
• scripts/quality_runners.py — module-context mode (--module-dir / --resolved-deps); calls ResolvedDependencies.overwrite
• scripts/aggregate_quality_report.py — new, consolidated report
• scripts/known_good/list_modules.py — new, dynamic Stage-2 matrix from known_good.json
• scripts/integration_test.py — derive build targets from known_good.json (drop build_config.json)

Resolved pins + their config ripple (kept together so the tree is self-consistent)

• known_good.json — pin bumps (baselibs, lifecycle) + per-module bazel_config + lifecycle code_root_path/extra_test_config
• bazel_common/score_basic_bazel.MODULE.bazel — flatbuffers bump
• bazel_common/score_modules_target_sw.MODULE.bazel — regenerated (baselibs, lifecycle)
• MODULE.bazel.lock — updated lock
• rust_coverage/BUILD — lifecycle query //src/... → //score/... (layout moved by the bump)
• showcases/simple_lifecycle/BUILD — lifecycle bin path //src/... → //score/launch_manager
• .bazelrc — coverage atomic-gcov / -no-coverage; eb-aarch64 outline-atomics link fix

Known Stage 2 integration findings (surfaced, not fixed here)

The workflow surfaces two module-owned integration failures caused by the
baselibs bump (score_logging CheckSizeValid stale uint8_t assumption;
score_persistency to_string on std::string_view).