[Feature]: ☂️ Iterative cap on sBTC

[djordon]

Feature - Iterative cap on sBTC

1. Description

We probably want a cap on the amount that can be pegged into sBTC, both at the transaction level and in aggregate. This will be a temporary cap that we lift as we become more confident that things are working correctly. Accomplishing that requires us to do two things:

1. Defining where which entity will be the authority of these limits
2. Configuring the signers to read and set these limits.

1.1 Context & Purpose

2. Technical Details:

The technical details nicely track the two items above. For the authority, we'll rely on Emily to set these limits. As for the signers, we already have started on the work to set these caps in #811.

2.1 Acceptance Criteria:

• We have finished the work in feat: sbtc limits handling in signer + emily integration #811 that gets the limits from Emily
• [Feature]: Add an endpoint in Emily for getting the sBTC cap #855
• [Feature]: In the signers we use the caps to filter out deposits #856
• (optional) we have a simple way of changing the cap in Emily #857
• [Feature]: Allow the bridge to prevent the user from depositing if it would violate a cap #859

3. Related Issues and Pull Requests (optional):

We have two design tickets for this:

• [Design]: Iterative Cap on Pegged sBTC #562
• [Design]: Cap on max sBTC pegged per transaction #791