refactor(ramp): transform aggregator network chain id to string

[wachunei]

Description

This PR prepares the Ramp codebase for an upcoming change in the Ramp API and Ramp SDK: the AggregatorNetwork['chainId'] will change from type number to string.

Places where it was being used as number have been changes to be used as string. Also, we now consider potential errors in places where the chainId was being transformed into a Hex string type (`0x${string}`), for example chainId with value "example" would have been involved in toHex(chainId) which would have thrown.

Once the Ramp API & SDK are updated, the transformation to string must be removed. This label marks the places it was done TODO(ramp, chainId-string):

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/RAMPS-1559

Manual testing steps

1. Go through the Ramp flows correctly

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: dfe8c63
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/dd776da9-ff81-47ed-83c2-321ad9ed8e1f

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[bkirb]

@wachunei LGTM for QA ✅

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 2506f57
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/3706e7f0-2a42-42a5-87e1-d8fee804653e

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[sonarqubecloud]

Quality Gate passed

Issues
8 New issues
0 Accepted issues

Measures
0 Security Hotspots
63.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud