Feat/OPDATA-6934 nobi ea

[mmcallister-cll]

Closes #OPDATA-6934

Description

Adds Nobi state price EA

Changes

• Added standard plumbing & WsTransport implementation
• Interesting part: NobiTransportManager in src/endpoint/transportManager that controls request routing based on a max number of WS subscriptions per connection and max number of connections per key (see ticket for details)

Steps to Test

1. yarn test nobi
2. with payloads

{
    "data": {
        "endpoint": "price",
        "base": "BTC",
        "quote": "USD"
    }
}

Set MAX_SUBSCRIPTIONS_PER_TRANSPORT sufficiently low (eg: 2) and request other common crypto pairs (eg: ETH/USD, SOL/USD) to see transport rollover

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.
• 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: dc1a2c5

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

This PR includes changesets to release 1 package

Name	Type
@chainlink/nobi-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

[mxiao-cll]

Why are these not in packages/sources/nobi/src/config/index.ts

[mmcallister-cll]

I think they could be, but then we'd have to lazy load the transport manager as a singleton

[alejoberardino]

PR with suggested approach: #5021

[alejoberardino]

should use this

[alejoberardino]

I get why but it's way too much imo, I don't believe having this be configurable is a good thing. I'd still loop and make 10 transports (the documented max connections) and have max subs as a proper config (which you could since the only place we'd need it is in the customRouter I think)

If we do see this as a repeated pattern (haven't so far afaik) and want to build some more complex abstracted logic we should put this in the fw