release-22.1: kvserver/loqrecovery: persist new replica ID in RaftReplicaID

[blathers-crl]

Backport 2/2 commits from #80470 on behalf of @erikgrinaker.

/cc @cockroachdb/release

---

cli: persist new replica ID in unsafe-remove-dead-replicas

The recently introduced local RaftReplicaIDKey was not updated when
unsafe-remove-dead-replicas changed the replica's ID. This could lead
to assertion failures.

Touches #75133.
Touches #79074.

Release note: None

kvserver/loqrecovery: persist new replica ID in RaftReplicaID

The recently introduced local RaftReplicaIDKey was not updated when
loss of quorum recovery changed the replica's ID. This could lead to
assertion failures.

Release note: None

---

Release justification: fixes an internal invariant violation which we'll start relying on in 22.2.

[blathers-crl]

Thanks for opening a backport.

Please check the backport criteria before merging:

• Patches should only be created for serious issues or test-only changes.
• Patches should not break backwards-compatibility.
• Patches should change as little code as possible.
• Patches should not change on-disk formats or node communication protocols.
• Patches should not add new functionality.
• Patches must not add, edit, or otherwise modify cluster versions; or add version gates.

If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.

• There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
• The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
• New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
• The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

• What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
• Will this work in a cluster of mixed patch versions? Did we test that?
• If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

[cockroach-teamcity]

This change is