Feat/OPDATA-6509 support data engine v7 schema & returnAs: float

[mmcallister-cll]

Closes #OPDATA-6509

Description

Adds support for data-engine v7 report schema
Adds functionality to decimal scaling via returnAs: 'float' input param. Previous behaviour was truncate-only. Truncate is preserved as default behaviour for backward compatibility.

Changes

• Add exchangeRate-v7 (redemptionRate-v7) endpoint
• Added returnAs common inputParam to allow for scaling selection (+ required downstream code changes)
• Added tests
• Mock date in tests to ensure new additions don't affect snapshots moving forward

Steps to Test

1. yarn test data-engine
2. with payload

{
    "data": {
        "endpoint": "redemptionRate-v7",
        "feedId": "0x0007621b6f5eb0b5bd5a8bb3d52902b3e19498ba45781e5ddf92ce7e03d7ecef",
        "resultPath": "exchangeRate",
        "decimals": 0,
        "returnAs": "float"
    }
}

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

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

This PR includes changesets to release 5 packages

Name	Type
@chainlink/data-engine-adapter	Minor
@chainlink/glv-token-adapter	Patch
@chainlink/gmx-tokens-adapter	Patch
@chainlink/gold-adapter	Patch
@chainlink/tokenized-equity-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

[github-actions]

👋 mmcallister-cll, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

[mohamed-mehany]

Looks good, minor comments about edge cases

[mohamed-mehany]

When fromDecimals === toDecimals, the function returns immediately, bypassing the 'float' logic entirely. If someone passes decimals: 18 (same as native) with returnAs: 'float', they'd get the raw integer "1156789000000000000" instead of "1.156789".

[mmcallister-cll]

That looks right to me 🤔. The intent is to perform the same scale-to num_decimals operation as already exists (scale to a certain # of decimals *10^X), but preserve the floating point precision rather than truncating. Am I missing something?

[mohamed-mehany]

Ah I see, I thought "returnAs" meant always return the value as float-point decimal, but I guess it means to return as float only when scaling is required, as an alternative to truncation? maybe worth adding a unit test or 2 to explicitly document the expected behavior.

[mxiao-cll]

Why?

[mmcallister-cll]

float vs int

Use case is using in a multiply with implied-price. Prob most correct is to add multiply/divide by constant to implied-price, and then nest implied-price calling itself, but figured we already have scaling functionality here.

[mxiao-cll]

Yeah, I think we should update implied-price to multiply two numbers with decimals instead