Added new DLC-BTC-POR EA

[karen-stepanyan]

Closes DF-19884

Description

Added new DLC-BTC-POR source EA. The EA doesn't take any input params. It fetches a list of vaults from a contract and for each vault verifies the vault deposit balance and sums all verified balances.

Steps to Test

yarn test packages/sources/dlc-btc-por

Quality Assurance

• If a new adapter was made, or an existing one was modified so that its environment variables have changed, update the relevant infra-k8s configuration file.
• If a new adapter was made, or an existing one was modified so that its environment variables have changed, update the relevant adapter-secrets configuration file or update the soak testing blacklist.
• If a new adapter was made, or a new endpoint was added, update the test-payload.json file with relevant requests.
• The branch naming follows git flow (feature/x, chore/x, release/x, hotfix/x, fix/x) or is created from Jira.
• This is related to a maximum of one Jira story or GitHub issue.
• Types are safe (avoid TypeScript/TSLint features like any and disable, instead use more specific types).
• All code changes have 100% unit and integration test coverage. If testing is not applicable or too difficult to justify doing, the reasoning should be documented explicitly in the PR.

[changeset-bot]

🦋 Changeset detected

Latest commit: 99d181f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@chainlink/dlc-btc-por-adapter	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[alecgard]

This looks good! Feedback is mostly just for some extra context to be added in comments

[mmcallister-cll]

Looks good, I think the main worries are batching/upper limit testing and further chain expansion, but these shouldn't be immediate issues. Worst case we can discuss & handle in future sprints.

[karen-stepanyan]

Did some upper limit tests
10000 transaction checks (5 different transaction duplicated 2000 times)
70 concurrent requests to BITCOIN_RPC
took 2 minutes 16 seconds

5000 transaction checks (5 different transaction duplicated 1000 times)
30 concurrent requests to BITCOIN_RPC
took 2 minutes 24 seconds

5000 transaction checks (5 different transaction duplicated 1000 times)
50 concurrent requests to BITCOIN_RPC
took 1 minute 29 seconds

From my testing the RPC was able to handle 70 concurrent requests, depending on RPC and network latency maybe this is not the limit. In terms of overall time execution we also need to have some space for a EVM RPC call to get the vaults