fix: refactor blockaid metrics sync functions to async

[vinistevam]

Description

After this PR to use the Security alert API to get the supported chains via isChainSupported which now it's an async function and we saw that it is used across the Blockaid metrics in the mobile client. So this PR aims to refactor every place that uses it to support it asynchronously.

Related issues

Fixes: https://github.com/MetaMask/mobile-planning/issues/1893
Related: https://github.com/MetaMask/mobile-planning/issues/1870

Manual testing steps

1. Go to this test dapp and perform a regression test using "PPOM - Malicious Transactions and Signatures"
2. Check if metrics are going to Segment (the env SEGMENT_WRITE_KEY will be required to perform this test)

Screenshots/Recordings

test-ppom.webm

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile 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]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: c29298c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/7cff7b00-2194-41e4-b36d-33f7f6327c4e

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 7f8d052
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/1ee3b676-4758-4d72-a1ec-294a6f43029b

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

[jpuri]

Changes look great, I left some small feedbacks to be addressed.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: cb5c855
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/792556c7-b84c-4084-b428-1aa32bd10adc

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: bf51625
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/8b6dfeb9-bb62-4002-93d9-bf002edcf321

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
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud