Need ability to send from "transparent" pool or else exchange will confiscate funds

[AlwaysCompile]

The wallet forces people to shield and then it forces them to send from the orchard pool which is creating a usability nightmare Many exchanges will confiscate funds that come from the orchard pool.

The wallet should allow users to send from the pool of their choices. I recommend changing the "quicksend" and "send" to accept an optional "pool" parameter. It is easy to parse as a pool can never be mistaken for an address.

send ?[pool]? [address] [amount]

Where the pool parameter is optional.

For example:

send transparent t1.....xy 5000000
send sapling t1.....xy 5000000
send orchard t1.....xy 5000000

And for backwards compatibility the default non-specified would be "orchard" so the following would send from ochard:

send t1.....xy 5000000

I understand that you plan to support TEX addresses, but that is not enough. Some exchanges will not adopt TEX but still confiscate orchard pool funds. In addition, some exchanges may have rules that are different than Binances.

TEX address require that 1 hop exists between a transparent and an orchard pool. Some exchanges may have a 2 hop or 3 hop rule. As such, users need the ability to send their own transparent funds if needed, so they can meet exchange requirements.