[HOTFIX] ENS name being resolved correctly

[tommasini]

Description
When the user had a slower internet connection and it was really quick to press the confirm button, the button would be enabled but the address would not be ready yet. Because of that we only proceeded to the next screen with the ENS.

Proposed Solution
Now we ensure that we have on that screen the address of the ens to go to the amount screen.

Technical
This was due to a delay in the component state on the validation function that happens on pressing the confirm button. This hotfix's a solution but it's better that we refactor some of the validation logic of it.

Test cases
If you can slow down your internet, this could be done on browser stack or with the Network Link Conditioner on macos
Case 1:
(Repeat this many times until it happens)

• Try ti send some USDC
• Write an ens on the address input of Send screen and try to hit Confirm as fast as you can (For me I needed to use the enter of the Keyboard)
• Then write an amount on the amount screen
• On confirm screen check if the address is 0x0000000 (if it is this address is incorrect)

Issue

Progresses #5128

Checklist

• There is a related GitHub issue
• Tests are included if applicable
• Any added code is fully documented

[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.

[sethkfman]

LGTM