Key rotation: Verifier should support N keys

_Copied from https://github.com/99designs/http-signatures-ruby/issues/10_

---

Currently key rotation is difficult; the verifier needs to start verifying with the new key at the same moment the new key is used by the signer. In a high-traffic environment this can be near impossible without dropping requests.

It should be possible to pass multiple keys to the verifier, so that both old and new keys can be accepted for a period of time. Either N keys, or a static limit of two keys (current and previous) would work.

This could be represented by passing an array of keys per ID; using the first for signing, and using all of them for verification. Or… something else?

Look at the Verifier class to understand how it currently handles a single key. The change involves modifying it to accept an array of keys per key ID, likely in the constructor or verification method. Check existing tests for verification to see how to adapt them for multiple keys. 'Done' means the verifier can successfully verify signatures using any of the provided keys for a given ID.

索引モデルが issue の本文から書いたものです。