feat(cost): share physical resources and consume offline evidence

[zzylol]

Why

Refs #322. Provide shared physical-resource definitions and a conservative offline-evidence path for planning. This PR is the planner library foundation, not the backend-only execution prototype.

Before this PR

The planner lacked a versioned empirical provider and query-matched exact/sketch comparison. Analytical and measured resource fields were defined separately.

After this PR

• Centralize PhysicalResources<Cpu, Bytes>, ModeledCpu, MeasuredCpu, Measurement, and MeasuredResources in asap-types::resources.
• Analytical estimates and empirical sketch/exact records reference the shared dimensions: peak/retained memory, scan traffic, serialized size and disk occupancy.
• Keep modeled CPU operations distinct from measured build/update/merge/prepare/read CPU nanoseconds. Unknown dimensions remain unavailable.
• Preserve analytical JSON and archived flat v1 benchmark JSON through compatibility adapters; preserve measurement uncertainty and integer byte precision.
• Add versioned schemas, a minimal synthetic fixture, strict applicability matching, public CostModel integration and fixed-snapshot frequency comparison.

Example: changing compatible update evidence can change candidate ranking; missing, stale or mismatched evidence keeps conservative behavior. A missing preparation measurement is not assumed free for arbitrary algorithms. Observed errors never become formal guarantees.

Scope and related work

This PR contains core code, consumer migrations, schemas, tests and developer documentation (15 files). It contains no benchmark runners, large generated results or synthetic execution benchmarks.

• docs: define backend-driven o11y evaluation scope #358 is closed. Its three evaluation documents were moved to feat(planner): bind offline frequency evidence and preserve o11y fallbacks ASAPQuery-backend#524 in commit c2a632e; no evaluation documentation is pending merge into this planner repository.
• feat(planner): bind offline frequency evidence and preserve o11y fallbacks ASAPQuery-backend#524 owns sketch-bench production, OpenMetrics import, backend planning and actual data-plane execution.
• The current prototype target is /mydata/metrics.txt plus o11y queries -> backend -> ASAPPlanner -> backend execution, with no Collector or Prometheus runtime. Actual result equivalence must precede latency/resource-benefit claims. That prototype is still being implemented and is not claimed complete here.
• Original measurements remain archived at https://github.com/ProjectASAP/ASAPPlanner/releases/tag/offline-evidence-2026-09-08.

Validation

358 mapping tests and 163 shared-types tests pass. Workspace formatting and strict all-target/all-feature clippy pass. Backend integration against the published shared-resource commit passes 7 integration tests, 633 control-plane tests and 973 data-plane tests.

No automatic issue closure or merge. Earlier large artifact commits remain recoverable in history; review the aggregate Files changed diff.