T2869

This diff is UI + frontend validation only.

Upgrades the Send Token component to conditionally render the One to Many Token Send input based on the Multiple Recipients toggle, consistent with the Send component.

Smilar to XEC multisends, frontend validation here only checks if each token send amount is less than token.balance. The validation of the aggregate token send amount across all rows will be done in sendToken in the next diff

[Cashtab] [eToken multisends] Part 1/3 - Frontend scaffolding
[Cashtab] [eToken multisends] Part 2/3 - Upgrade sendToken to handle multisends
[Cashtab] [eToken multisends] Part 3/3 - Implement max limit of multi token sends

• npm test and ensure no snapshot errors
• npm start
• navigate to the Send Token component and toggle Multiple Recipients
• enter a valid ecash address, separated by comma, and a valid token amount and ensure no errors
• ensure no UI slowdown issues as you type each letter in the input field and it triggers the onChange logicaa
• enter an valid ecash address with 0 as the token amount and validate the 'Ensure each tx has a valid token amount' error is displayed
• enter an valid ecash address with a token amount higher than your token balance and validate the 'Ensure each tx has a valid token amount' error is displayed
• enter an invalid ecash address with a valid token amount and validate the 'Ensure each XEC address is valid' error is displayed
• enter a space and validate the 'Empty spaces and rows must be removed' error is displayed
• enter 3-4 rows of valid ecash address with a valid token amount and ensure no errors and console log message of 'Submitting a one to many token transaction' is displayed
• enable confirmation modal in settings, send a valid token multisend and ensure all outputs are displayed on the modal