Finalize CRUD operations for E.O.S Wallets

[KtorZ]

Context

Until here, we didn't need the remaining classic CRUD operations on E.O.S. wallets.

Decision

For completeness and because we want to make our users happy, let's implement (and test) them.

Acceptance Criteria

1. • The API must support 'Read' operation on E.O.S. Wallets.
2. • The API must support 'Update' operation on E.O.S. Wallets.
3. • The API must support 'Delete' operation on E.O.S. Wallets.
4. • The API must support 'List' operation on E.O.S. Wallets.
5. • The 'Update' operation from Finalize CRUD operations for E.O.S Wallets #36.2 may act upon the followings: name, assurance level, address gap.

---

PR

Number	Base
#278	develop
#304	develop

Consequences

[piotr-iohk]

@denisshevchenko, @KtorZ
There is no QA section on the ticket, however I understand that it is an old format. :)
In any case, in terms of QA, I think we should add some integration tests for CRUD operations. Probably we want to approach this in different task? (I haven't found any, so if there is one can you point me to it pls?).

There are some tests already added in #236. But they only touch on create and read. There are no tests covering list, update, delete.

[KtorZ]

Indeed there's no QA / tests for this yet. I'll leave that decision to @denisshevchenko here; would you rather write them as part of this ticket? Or should we open another ticket a bit like #236 where you or I can write those integration tests?

[piotr-iohk]

@denisshevchenko I'm closing this one. As discussed I'll be adding more integration tests for EOS wallets CRUD operations under #331.