Nodejs no reconnect or event after energy mode

### Describe the bug
There is no reconnect or connection failure when switching to energy-saving mode.

### To Reproduce

`
let client = new WebPubSubClient(url);
client.on("connected", (e) => {
console.log(`Connection ${e.connectionId} is connected.`);
});
client.on("disconnected", (e) => {
console.log(`Connection disconnected: ${e.message}`);
});
client.on("stopped", async () => {
console.log(`Client has stopped`);
});
`

1. Connect
2. Go 60 s in energy consumption mode
3. Start computer
4. It looks like there is a connection, but no more messages are being received. No reconnect and no event is created.
All the time no new information as "Connection ******************** is connected." But this is not true.

### Further technical details
- Actual SDK Nodejs NPM package "@azure/web-pubsub-client": "^1.0.0",

Start with the @azure/web-pubsub-client Node.js package and reproduce the energy-saving suspend-and-resume steps using the connected, disconnected, and stopped handlers shown in the issue. Trace how the client detects a lost connection after resume; done means it reconnects or emits an appropriate connection-failure event instead of appearing connected while receiving no messages.

Written by the indexing model from the issue text.