feat: Query By Recipient

[AshtonStephens]

Description

Closes: #1122

Changes

This PR adds a new endpoint to emily. Unfortunately, the client autogeneration stopped working when I made the status optional in the get_deposits query, and I couldn't find any autogenerated solution, so to resolve this I've added a new endpoint:

https://{base_url}/deposit/recipient/{recipient}.

It works much like the other query but has the recipient in the path. This is a departure from the rest implementation, but it's the only way I could get it working.

In order to support this, there's now a new deposit table index that can be accessed by recipient.

Testing Information

Tested with an integration test in this PR.

Checklist:

• I have performed a self-review of my code
• My changes generate no new warnings
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[Jiloc]

Given that we are not rushing this feature, would it make sense to have another time-gated effort to try it to make it work with the get_deposits endpoint as a query? If you think that's just time wasted, I am fine with going forward as it is

[Jiloc]

Given that we are not rushing this feature, would it make sense to have another time-gated effort to try it to make it work with the get_deposits endpoint as a query? If you think that's just time wasted, I am fine with going forward as it is

As discussed, an important time was already allocated for this and there was no apparent workaround. We are fine with the current approach after @MCJOHN974 comments are solved

[MCJOHN974]

LGTM! (But since I'm new for the repo suggest to wait until @Jiloc adds a review)