feat: automatic revocation registry regeneration

Problem to solve

Revocation Status Lists have a maximum number of credentials that can be issued with it. (In our case: 100) Once this limit is reached - the same revocation status list cannot be used, because all of its indices are filled up with credentials, and a new list must be created for the same credential definition.

Proposal

Along with the issue #94 and using the results from it, we should track when the revocation status list fills up, and once it is full - we should automatically create a new one and use it for subsequent revocable credentials issuing.

Additional Notes

• What strategy should we take on selecting the revocation definition id, because if it is automatically generated, it should not be passed in the credential body.