hummingbot: Ascendex - Getting "unexpected error occurred when listening to orderbook streams" when the bot is stopped or killswitched for a long time

Describe the bug For monitoring purpose: While checking long term bots, we noticed that for Ascendex after the client has been stopped due to triggered killswitch there was returning error of Unexpected error occurred when listening to orderbook streams...

Based on the screenshot below, it seems that the bot had stop 9:38:21 due to killswitch and return the error at 11:16:04 with different time intervals

2022-08-18 11:22:13,547 - 1694 - hummingbot.connector.exchange.ascend_ex.ascend_ex_api_order_book_data_source - ERROR - Unexpected error occurred when listening to order book streams. Retrying in 5 seconds...
Traceback (most recent call last):
  File "/home/rapcmia/github/dev/hummingbot/connector/exchange/ascend_ex/ascend_ex_api_order_book_data_source.py", line 262, in listen_for_subscriptions
    async for ws_response in ws.iter_messages():
  File "/home/rapcmia/github/dev/hummingbot/core/web_assistant/ws_assistant.py", line 69, in iter_messages
    response = await self._connection.receive()
  File "/home/rapcmia/github/dev/hummingbot/core/web_assistant/connections/ws_connection.py", line 62, in receive
    msg = await self._process_message(msg)
  File "/home/rapcmia/github/dev/hummingbot/core/web_assistant/connections/ws_connection.py", line 84, in _process_message
    msg = await self._check_msg_types(msg)
  File "/home/rapcmia/github/dev/hummingbot/core/web_assistant/connections/ws_connection.py", line 89, in _check_msg_types
    msg = await self._check_msg_closed_type(msg)
  File "/home/rapcmia/github/dev/hummingbot/core/web_assistant/connections/ws_connection.py", line 99, in _check_msg_closed_type
    raise ConnectionError(
ConnectionError: The WS connection was closed unexpectedly. Close code = 1000 msg data: None
2022-08-18 11:22:18,849 - 1694 - hummingbot.connector.exchange.ascend_ex.ascend_ex_api_order_book_data_source - INFO - Subscribed to ['XRP-USDT'] orderbook trading and delta streams...

We tried to reproduce by disconnecting to internet while the client is running but no avail. However when we stopped the bot and left it for a while it displayed the error after 2mins. See screenshot below

While this happened when it is stopped, we didn’t notice any of the errors when the Hummingbot client is running long term.

Steps To Reproduce

1. Setup simple Pure market making or Liquidity mining strategy
2. Run the client for a good 3-5mins then stop or trigger killswitch
3. Dont close the client and leave it for a good 15-30mins (its a hard to reproduce since there different time intervals on the log file w have)

Release version Development dev-1.7

Attachments logs_conf_liquidity_mining_2.zip