feat(network)!: require PeerId in persistent peers configuration

[melekes]

Closes: #1486

Requires `PeerId` in every persistent peer address (e.g. `/ip4/1.2.3.4/tcp/9000/p2p/12D3KooW...`). Config and API now require the `/p2p/<peer_id>` component.

Changes

• Validation: `spawn()` and `add_persistent_peer()` validate that each address includes a PeerId; return `PersistentPeerError::PeerIdRequired` otherwise.
• Identity verification: On connection, if the address matches a persistent peer, the connected peer's PeerId is checked against the expected one; on mismatch the peer is rejected and disconnected.
• Discovery: Bootstrap addresses can carry an optional PeerId; it is extracted when present.

Breaking change

Documented in `BREAKING_CHANGES.md`: persistent peer addresses must include `PeerId` (e.g. `/ip4/1.2.3.4/tcp/9000/p2p/12D3KooW...`).

---

PR author checklist

Contribution eligibility

• I am a core contributor, OR I have been explicitly assigned to the linked issue
• I have read CONTRIBUTING.md and my PR complies with all requirements
• I understand that PRs not meeting these requirements will be closed without review

For all contributors

• Reference a GitHub issue
• Ensure the PR title follows the conventional commits spec
• Add a release note in RELEASE_NOTES.md if the change warrants it
• Add an entry in BREAKING_CHANGES.md if the change warrants it

For external contributors

• Maintainers of Malachite are allowed to push changes to the branch