feat: improve bridge admin controls

[thiennamdinh]

Summary

• Add explicit bridge admin sections for subscribing to peers and publishing to peers, including endpoint editing, delete actions, and push/pull/none policy controls.
• Preserve disabled bridge/subscriber entries as none tombstones while adding explicit delete operations for removing incoming bridge and outgoing subscriber config.
• Stop writing stale bridge/subscriber local snapshots, expose local journal name in public config for remote-name autofill, and skip disabled incoming bridge sync during step.
• Refresh stale architecture notes by consolidating current cross-journal data-flow ideas and removing superseded idea documents.
• Make ledger binary releases use VERSION as the source of truth: main commits that change VERSION now publish ledger-v<VERSION> release assets from the validated binary artifacts.
• Bump platform/package versions to 1.4.2.

Testing

• ./records/tests/test.sh ./journal/target/debug/journal-sdk
• node scripts/sync-platform-package-versions.js
• cd services/explorer && npm test -- --watchAll=false
• cd services/explorer && npm run build
• cd services/gateway && npm test -- --runInBand
• cd docs/info && npm run build
• Playwright smoke against local 4-node ACTIVITY=1 social-agent stack: login, create/edit/disable/delete subscribed bridge, create/delete publishing bridge, verify remote-name autofill and ledger config effects.

Notes/Risks

• journal-sdk crate version remains 1.3.1; this PR bumps the platform/service package version only.
• Ledger binary publishing is now tied to main VERSION changes and guards against reusing an existing ledger-v<VERSION> release tag from a different commit.
• Existing Explorer build warnings remain for hook dependency lint checks; docs build still reports existing Starlight duplicate-index and Pagefind/DEP0190 warnings.