fix: cp-7.47.0 Add safe checksum method in SendTo page

[OGPoyraz]

Description

This PR aims to fix an issue when user puts an unexpected value into to field in send flow.

It appears from that the issue is thrown by toChecksumAddress because it doesn't expect any incomplete address. However in send flow UX we let user to type in address themselves.

To test this you can go SendTo page and put K for example - and see the crash. (Screenshot below is fixed version)

Labels
Adding skip-sonar-cloud as the raised issue was intentional.

Related issues

Fixes: #15094

Manual testing steps

1. Go to send flow
2. Input an unexpected address
3. Confirm warning shown - you shouldn't be proceed next step

Screenshots/Recordings

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]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 86334a5
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/a5d33af6-6baf-4925-913a-249ca161c4e8

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 failed

Failed conditions
C Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE