Issued certificates versioning

[tgragnato]

Feature Request

Q	A
New Feature	yes
RFC	yes
BC Break	no

Summary

The versioning of issued certificates by an internal certification authority (CA) is a recommended practice for several reasons:

1. Traceability: Versioning allows tracking and managing various versions of a certificate over time. This is particularly important for monitoring and issue resolution, as it quickly identifies which version of a certificate is currently in use or has been revoked.
2. Updates and Renewals: When a certificate needs to be renewed or updated (e.g., due to a compromised key or other changes), versioning facilitates the process. Each new version can clearly indicate changes made compared to the previous version.
3. Compliance and Auditing: Versioning contributes to compliance with regulations and simplifies security audits. Regulatory bodies and security inspectors can review the version history to ensure that the CA is following proper procedures and managing certificates appropriately.
4. Communication and Notifications: In the event a certificate needs to be revoked or replaced promptly, versioning provides a clear way to communicate to users or other relevant systems that a new version of the certificate is available.

This feature request involves implementing an additional set of APIs and expanding the interface of the persistence layer (storage) to support this functionality.