fix(analysis): normalize memory metadata and traffic

[zhen8838]

Why

• Memory results were split across three metadata types and three report families, while Function traffic undercounted loop-invariant movement.

What

• Replace the old traffic, loop-footprint, and placement attachments with MemoryMetadata on Calls and RegionMemoryMetadata on the Function under one memory report family.
• Remove the known-invalid authored-loop footprint and report-layer cache-pressure reconstruction; uncomputed footprints are explicitly null.
• Accumulate logical, total, and per-unit traffic independently so total and per-unit include every executed enclosing-loop occurrence.
• Add a hand-calculated invariant-read fixture, exact report expectations, updated consumers, specs, goldens, and generated tutorials.

Contract

• This is an intentional breaking replacement: old metadata types, aliases, and traffic/loop-footprint JSON families are removed rather than projected for compatibility. LoopRegion receives no empty memory record. A successful RegionMemoryMetadata record has required solver_status=feasible.

Risk

• Consumers of the old Python types or JSON families must migrate to the new memory records. Correct read footprints and L2 capacity advisories remain follow-up work; footprint is null until that analysis exists.

[zhen8838]

You don't need to test all of them, just test the key parts.