the websocket monitoring is hanging, need to review the MonitorTransaction function

[artemijspavlovs]

need to review the function, there are 2 flavors of websocket endpoints,

http - when the websocket is exposed at /websocket of the dymint rpc
ws - when there's a separate

we assume use the http right now, because of that for some hub endpoints, the transaction is not monitored properly

We should add an optional field to the roller config named wss_endpoint, if it is set, then use that as the endpoint for MonitorTransaction, otherwise default to the rpc endpoint's /websocket path