fix: use the same peer id to load and store peer records

[tabcat]

Description

consumePeerRecord() uses two different peer ids. It derives one from the
envelope public key and uses it to load the stored peer and compare sequence
numbers, then stores the addresses under the peer id from the record payload.

A PeerRecord names the peer it describes, so for anything produced by
RecordEnvelope.seal() the two agree and this is invisible. Nothing checks it
though, and when they differ the sequence number comparison is made against a
different peer to the one being written, so it no longer orders that peer's
records and an older record can replace a newer one.

Ignore records where the two do not match.

Notes & open questions

Returns false like the neighbouring expectedPeer check rather than throwing.

Change checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation if necessary (this includes comments as well)
• I have added tests that prove my fix is effective or that my feature works