AnonCreds: Automated setup of revocation artifacts

[dbluhm]

Setting up revocation requires fairly intimate knowledge of how revocation works in AnonCreds. Historically, with the first implementation of revocation in ACA-Py, this responsibility was left to the controller. However, we've determined this is too much of a burden to place on Controller authors.

While implementing the ledger agnostic anoncreds interface, as a temporary solution while building up all the various required components, we added endpoints similar to the original revocation endpoints that made it the controllers responsibility to setup revocation. This should not be the final setup.

[dbluhm]

Completed by #2292