… `SendTo` page (#15308)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

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](https://metamask.sentry.io/issues/6582066742/?project=2299799) 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.

![Screenshot 2025-05-14 at 06 44
09](https://github.com/user-attachments/assets/fda651bc-4925-40d8-95ca-2cabd7cbed66)

## **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**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [X] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [X] I've completed the PR template to the best of my ability
- [X] I’ve included tests if applicable
- [X] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [X] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
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.