Reconstruct tests to self host tracker server and peers

[artrixdotdev]

Problem

Facade-level tests should not depend on public trackers, public peers, or mutable internet state. The crate needs local/self-hosted components to exercise frontend behavior deterministically.

Consolidation

This is the canonical issue for deterministic fake/self-hosted tracker, peer, and storage test harnesses. It supersedes duplicate #244.

Acceptance criteria

• Add or document fake/local tracker support for tests.
• Add or document fake/local peer behavior sufficient for facade lifecycle/events/snapshots tests.
• Add deterministic storage fixtures for piece/progress paths where needed.
• Public-network tests remain ignored and are not required for default CI.
• New harnesses are reusable across facade tests.

[artrixdotdev]

Claiming this in branch test/reconstruct-self-hosted-tracker-and-peers. I’ll focus on reusable deterministic local tracker/peer/storage test harness pieces for libtortillas facade work.