[DF-22956] ensure tiingo request transform executes by removing factory wrapper

[guandali]

Closes #DF-22956

Description

Refactor tiingoCommonSubscriptionRequestTransform from a factory function to a direct request transform to align with the AdapterEndpoint contract.

Changes

Before

export function tiingoCommonSubscriptionRequestTransform() {
  return (req) => { ... }
}

After

export const tiingoCommonSubscriptionRequestTransform = (req) => { ... }

Steps to Test

1. Steps
2. to
3. test

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: b0e9980

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

This PR includes changesets to release 9 packages

Name	Type
@chainlink/por-address-list-adapter	Patch
@chainlink/tiingo-adapter	Patch
@chainlink/itick-adapter	Patch
@chainlink/token-allocation-adapter	Patch
@chainlink/bsol-price-adapter	Patch
@chainlink/crypto-volatility-index-adapter	Patch
@chainlink/savax-price-adapter	Patch
@chainlink/set-token-index-adapter	Patch
@chainlink/xsushi-price-adapter	Patch

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

[cl-efornaciari]

one question, also needs to be rebased

[cl-efornaciari]

Is this an actual case? is this assumed to be USD?

[guandali]

USD

[cl-efornaciari]

Should this update tiingo-state as well?

[mxiao-cll]

For major bump always include details on that what is breaking and how should NOP handle it

[guandali]

i downgraded it patch
changeset won't list tiingo-state as option, i think in this PR it is implicitly modified

[mxiao-cll]

This makes no sense, you only updated tiingo

[mxiao-cll]

I don't understand what toBe is doing here