feat(peer): recover accepted relay anchors

[M4n5ter]

Summary

• persist only identity-checked Circuit Relay v2 reservations that the relay actually accepted
• reacquire those relay anchors after endpoint restart with bounded retries, demoting an anchor only after repeated failure
• keep advertised coordination routes synchronized with the currently accepted reservation set
• preserve manual relay configuration while making recovered public relay availability survive process churn

Refs #4554

Verification

Verified on the complete stacked head after rebasing from main at eacfb46aa7ec93273bf468335f4270bba62d35a5:

• npm run typecheck
• npm run lint
• npm run format:check
• npm run rebuild
• npm run test:dist - all workspace tests passed
• npm run check:renderer-architecture - 71 passed
• npm run check:release - 192 passed
• git diff --check
• cargo fmt --manifest-path native/runtime-host-peer/Cargo.toml -- --check
• cargo clippy --locked --all-targets --manifest-path native/runtime-host-peer/Cargo.toml -- -D warnings
• cargo test --locked --manifest-path native/runtime-host-peer/Cargo.toml - 27 passed
• immutable installed-CLI tarball smoke

Review focus

A discovered HOP-capable peer is not an anchor. Only a successful Relay v2 reservation becomes advertised recovery evidence, and reference ownership is released when that evidence is replaced.

AI use

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: Codex implemented and verified the change under maintainer direction.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes - described under Summary above
• No