Improve UX for manually add assets

[JakeUrban]

"curious if we've thought about trying to get rid of the "add an asset" vs "add manually" choice in this flow?
I've seen users get confused by this because they don't know when to search manually or how it's different from the regular search.
Under the hood, one does an asset search and the other does either a contract id or issuer lookup depending on if you enter a G or C key.
I think we can pretty much do the same thing while using one input by parsing the input into: asset code or contract id or public key and doing the search that matches the input type." - @aristidesstaffieri

[aristidesstaffieri]

"curious if we've thought about trying to get rid of the "add an asset" vs "add manually" choice in this flow? I've seen users get confused by this because they don't know when to search manually or how it's different from the regular search. Under the hood, one does an asset search and the other does either a contract id or issuer lookup depending on if you enter a G or C key. I think we can pretty much do the same thing while using one input by parsing the input into: asset code or contract id or public key and doing the search that matches the input type." - @aristidesstaffieri

Yeah absolutely, this has been flagged as an improvement for a long time but never prioritized. There is no reason why we can't do this now. I think along with this, we should improve our ability to reject contracts that are not sep41 compliant. Right now we accept any valid contract ID.