Handle keyset rotations

[gudnuf]

If we have a pending mint operation in our database (like a cashu-send-swap) that specifies a keyset ID and the mint rotates active keysets, then we will never be able to complete that operation. It is okay for inputs to a mint operation to be from an inactive keyset, but if we are creating outputs they must be from an active keyset.

I have only noticed inactive keyset errors when the mint rotates keys in between a mint operation being drafted and being completed. Our wallet seems to handle keyset rotations well otherwise.

P.S. We should also prefer to use proofs from inactive keysets (see cashubtc/cashu-ts#370)

[jbojcic1]

@gudnuf is this duplicate of #131

if yes please close one

[jbojcic1]

There is also this one #379

[gudnuf]

More details:
If we create some transaction where we commit to output data from a specific keyset ID and then the mint rotates theirs keys this keyset ID will no longer be active. We cannot use this output data to create proofs because the keyset is now inactive.