Port Kiwiing APIs in KERIpy to KERIA - Issue, Present, and Verify with KERIA and Signify

[kentbull]

In order to issue credentials with KERIA and Signify, as well as the other credential actions present and verify, all of the relevant APIs from kiwiing.py must be ported to KERIA and Signify.

The APIs are not a one-to-one port since the architecture of KERIA is different than KERIpy.

[kentbull]

Here’s a spreadsheet comparing the REST APIs of both KERIpy and KERIA: KERIpy-KERIA-Signify comparison
This will help us keep track of the work that needs to be done, if something like this doesn’t already exist.
From the looks of things most, if not all, of the KERI work is done in KERIA. The primary work remaining unfinished is the ACDC work.

Here’s a list of the work that isn’t done. Some of it may not need to be done and the REST routes between KERIpy and KERIA are not one-to-one:

1. Finishing registry inception - refactoring to a long-running Op.
2. Refactor registrar to support Signify event creation.
3. Credential Issuance
   POST /credentials/{name}
4. Credential Revocation
   DELETE /credentials/{name}
5. Credential Presentation
   POST /credentials/{name}/presentations
   POST /credentials/{name}/requests
6. Credential Retrieval
   GET /credentials/{name}
7. Credential Export
   GET /credentials/{name}/{said}
8. Multisig Group Creation
9. Multisig Group Credential Issuance
   POST /groups/{name}/credentials
   PUT /groups/{name}/credentials
10. Multisig Group Credential Revocation
    POST /groups/{name}/credentials/{said}/rev
    PUT /groups/{name}/credentials/{said}/rev
11. Multisig Group Credential Presentation?
12. Escrow statuses
    GET /escrows
    GET /escrows/{pre}/{dig}
13. Codes ported to SignifyPy?
    GET /codes
    POST /codes
14. Mailbox? Server Sent Events?
    GET /mbx
15. receipts?
    GET /receipts