Better handling for long running (timed out) chat requests

[backwardsmap]

Describe the bug
Some requests (e.g., executing a swap that is slow to confirm the RPC sent off the transaction) may run for too long (current timeout for chat message route is 30 seconds), or not complete entirely.

Currently when this occurs, the running tool just hangs and never gets a response.

Implement a better way to gracefully handle situations like this, and pass some sort of human readable timed out / try again message back to the client.

[briang123]

I noticed that the chat session ended way too early, as well.