refactor: cleanup AccountInput and remove RecipientAccountSelector

[VmMad]

Summary

Fixes #7172
Fixes #7268

• Unify RecipientAccountSelector and AccountInput into a single component
• Rename AccountInput to AccountSelector

...

Changelog

- Please write a list of changes

Testing

Platforms

Please select any platforms where your changes have been tested.

• Desktop
  • MacOS
  • Linux
  • Windows
• Mobile
  • iOS
  • Android

Instructions

Please describe the specific instructions, configurations, and/or test cases necessary to test and verify that your changes work as intended.

...

Checklist

Please tick the following boxes that are relevant to your changes.

• I have followed the contribution guidelines for this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or modified tests that prove my changes work as intended
• I have verified that new and existing unit tests pass locally with my changes
• I have verified that my latest changes pass CI workflows for testing and linting
• I have made corresponding changes to the documentation

[evavirseda]

LGTM 🚀

[begonaalvarezd]

Im not sure we want to remove this component, it looks like a good reusable component to me, even though its only used once, it might be able to be used later on. Perhaps what we could do is call it like AccountSelector or AccountInputSelector or something like that because its not really an input, wdyt?

[cpl121]

lgtm

[begonaalvarezd]

It would have been interesting clean it up so the modal component ends up being reusable for other places, atm we have it for deep links and the send flow, and its practically the same modal, just the information displayed differs a bit.

But for now I think its ok