Decouple KeyPairResource ID from keyID

[paullatzelsperger]

Feature Request

Currently we use KeyPairResource#id and KeyPairResource#keyId almost interchangeably. This is not good, because it prevents having multiple KeyPairResource objects with the same keyId.

This gets problematic when the database is supposed to contain multiple KeyPairResource objects with the same keyID, but possibly different status flags (rotation, revocation,...). That would cause conflicts.

Which Areas Would Be Affected?

KeyPairResource API + underlying layers

Why Is the Feature Desired?

KeyPairResource#id is the data base ID, which should be decoupled from the keyId.

Solution Proposal

• add an optional resourceId field to the KeyDescriptor, that - if set - determines the KeyPairResource#id. If left blank, a random UUID is used.
• adding KeyPairResources through the API follows the same scheme