Move edge-agent logic to agent-sdk

[rolsonquadras]

Idea is to create simplified APIs that can be used by sdk, browser(js/wasm binding), mobile native(gomobile), rest bindings for the business logic present in edge-agent (currently, it's written in Javascript). Instead of repeating these in individual bindings, we need to move the JS code to Golang code and expose them through different bindings.

The list includes

• wallet login (create DID, register with mediator)
• DIDComm/AuthZ logic with issuer/rp
• etc

[sudeshrshetty]

Modules identified by wallet implementations

Reference: edge-agent wallet implementation

1. Presentation Exchange - expected to be part of aries-framework-go
2. Blinded Routing - To be implemented in agent-sdk as a new command package
3. Mediator Client - All generic mediator client logic needed by wallet.
4. DID Manager - Portion of this can be moved to agent-sdk only if required(very unlikely)
5. Get credential by query - AuthZ, credential search logics to be moved to agent-sdk from wallet implementation
6. Wallet Registration & on-boarding - portion of this wallet implementation can be moved to agent-sdk if required(very unlikely)

7. Storage - currently being used by wallet manager & did manager for saving metadata

   Note: All credential handler request/response handling will stay in edge-agent for now, credential handler api bridge is yet to be implemented.

[sudeshrshetty]

Tasks

• [x] mediator client #56 #57
• [x] blinded routing #74
• [x] DID Manager
• [x] Get Credentials
• [x] Presentation Exchange
• [x] Wallet Registration
• [x] Wallet Storage