bug: http_client WS breaks Kinode Req/Res

[nick1udwig]

Describe the bug
Client WS Pushes break Kinode Request/Response mental model just like how Server WS pushes used to (resolved in #218)

To Reproduce

1. Receive a Request (id 123) you want to eventually Respond to
2. Do some work involving WS client, receiving pushes (which are always Requests, and hence, reset the prompting_message)
3. Try to Respond

Instead of routing to 123, it will route to http_client.

Expected behavior
Route to 123.

The fix

Requires some thought. In #218 it was assumed we'd always have a Req/Res happening. In my particular usecase, I am connecting to a WS, receiving some arbitrary number of pushes, and then closing the connection.

One hack we can do is when connecting to the WS, you can set if you want to be receiving Requests or Responses from the server. This fixes my case but not the general case.

[nick1udwig]

This makes me think the #218 solution may not be sufficiently general either.