Troubleshoot reliability of interactive features

[salieflewis]

1. Ensure the create channel feature always works

• Loading states are transparent
• Users always get pushed to the appropriate route
• Appropriate route always shows data

2. Ensure the add to channel feature always works

• Loading states are transparent
• The UI updates without the need to manually refresh
• Error handling is implemented
• Disabled states are transparent

[0xTranqui]

Throwing some thoughts in about how to approach improving the reliability of the "push to appropriate route following channel creation"

• I have a hunch that this can be accomplished by adding some type of client side getter that starts pinging the DB upont transactionReceipt showing up as NOT null, and then continuing to do that until the target channel query returns a non null meaning that it has been processed by the DB and is safe for us to redirect the user there. this will prevent the current non process aware implementation that just hardcodes a timeout value
• not sure of the specific implementation details of how to accomplish this, but something in to this effect could be effective

cc @salieflewis