Swarm: handle expiration changed

When a certificate got expired, it can be renewed with a new expiration. Swarm must be updated for new messages.

This needs some preparative work:

First, the migration behaviour should be fully validated and testable/automatized, this is currently in progress (https://review.jami.net/c/jami-daemon/+/20112, https://github.com/savoirfairelinux/opendht/pull/573)

A few tests must be added (This part is now in review https://review.jami.net/c/jami-daemon/+/20120):

• If a device is expired, check that the migration is updating the same device's expiration (in progress, seems not the case)
• If an account is expired, check that the migration is updating the same certificates
• If device is revoked, a new device should be generated

Then, once this is validated, we will need to add some tests for:

• After a device migration, the account should be able to commit on a swarm
• After an account migration, the account should be able to commit on a swarm

This part is in review https://review.jami.net/c/jami-daemon/+/20127