MaxListenersExceededWarning No events are triggering
### Is there an existing issue for this?

- [X] I have searched the existing issues

### Describe The Bug

So starting about a week ago all events stopped going to my application, it hasn't changed in the last year or so but something happened (not sure what day exactly) where all the events are coming through. I first thought that there was an update to the Ring API and I'd have to update the ring-api-cli npm version (which I've done in the past and it works), but this time I was debugging locally and on the deployed server and I am getting a warning stating "MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ON_READY listeners added to [PushReceiver]. Use emitter.setMaxListeners() to increase limit", I ran it with --trace-warnings and got the following stacktrace.

Looks like it has something to do with the @eneris\push-receiver library, my package.json is pretty clean with only this library and axios as a depedency. Any help would be appreciated.

```
{
  "name": "ringlistener",
  "version": "1.0.0",
  "description": "",
  "main": "server.mjs",
  "dependencies": {
    "axios": "^0.21.1",
    "ring-client-api": "^12.0.0"
  },
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC"
}

```

```
import {RingApi} from 'ring-client-api'
import * as ringTokenLoader from './RingTokenLoader.js';
import * as configLoader from './ConfigLoader.js';
import * as webPost from './WebPost.js';
var config = configLoader.generateConfig();
var currentToken = ringTokenLoader.generateConfig();
var lastRunTime = new Date();
start();
async function start() {
    console.log("Starting Ring Listener at the time " + (new Date()).toISOString());
    if (currentToken == null){
        console.log("Current Token is null");
        return;
    }
    const ringApi = new RingApi({
        refreshToken: currentToken,
        cameraDingsPollingSeconds: 2
    });
    const allCameras = await ringApi.getCameras();
    console.log(
        `Found ${allCameras.length} camera(s).`
    )

    ringApi.onRefreshTokenUpdated.subscribe(
        async ({newRefreshToken, oldRefreshToken}) => {
            console.log('Refresh Token Updated: ');
            if (!oldRefreshToken) {
                console.log("It returned cause not oldRefreshToken: " + oldRefreshToken);
                return
            }
            currentToken = ringTokenLoader.writeRefreshToken(newRefreshToken);
        }
    )
    if (allCameras.length) {
        allCameras.forEach((camera) => {
            camera.onMotionDetected.subscribe((data) => {
               console.log("Motion was detected AT " + (new Date()).toISOString());
            });
            camera.onDoorbellPressed.subscribe((data) => {
                console.log(
                    `Ring doorbell pressed on ${camera.name} camera. Ding id ${
                        data.ding.riid
                    }.  Received at ${new Date()}`
                )
            })
        })

        console.log('Listening for motion and doorbell presses on your cameras.')
    }
}
```

### To Reproduce

Not sure but I stripped my application down to the bare minimum, just events listing for tokenRefresh, motion, and doorbell press. Leaving the application running triggers the stacktrace below after about 30 seconds, and any event committed on the ring device shows up on my phone, but nothing is received on these events from the node app.

Also the two "Motion was detected AT*" messages happen on every startup, regardless if there is motion or any other type of ding. It doesn't actually signify a motion that was recorded

```
Configuration file found at /mnt/RingConfig.json
Configuration file found at /mnt/RingListener.cfg
Starting Ring Listener at the time 2023-09-05T04:02:31.041Z
Found 2 camera(s).
Refresh Token Updated: 
Updated new refresh token
Motion was detected AT 2023-09-05T04:02:31.967Z
Motion was detected AT 2023-09-05T04:02:31.967Z
Listening for motion and doorbell presses on your cameras.
(node:23020) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ON_READY listeners added to [PushReceiver]. Use emitter.setMaxListeners() to increase limit
    at _addListener (node:events:587:17)
    at PushReceiver.addListener (node:events:605:10)
    at PushReceiver.on (Z:\Docker\RingListener\node_modules\@eneris\push-receiver\dist\client.js:78:51)
    at PushReceiver.onReady (Z:\Docker\RingListener\node_modules\@eneris\push-receiver\dist\client.js:96:14)
    at Z:\Docker\RingListener\node_modules\@eneris\push-receiver\dist\client.js:127:34
    at new Promise (<anonymous>)
    at Timeout.connect [as _onTimeout] (Z:\Docker\RingListener\node_modules\@eneris\push-receiver\dist\client.js:126:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
```


### Expected behavior

That the events fire and I get the message logged to console.

### Relevant log output

```shell
Configuration file found at /mnt/RingConfig.json
Configuration file found at /mnt/RingListener.cfg
Starting Ring Listener at the time 2023-09-05T04:02:31.041Z
Found 2 camera(s).
Refresh Token Updated: 
Updated new refresh token
Motion was detected AT 2023-09-05T04:02:31.967Z
Motion was detected AT 2023-09-05T04:02:31.967Z
Listening for motion and doorbell presses on your cameras.
(node:23020) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ON_READY listeners added to [PushReceiver]. Use emitter.setMaxListeners() to increase limit
    at _addListener (node:events:587:17)
    at PushReceiver.addListener (node:events:605:10)
    at PushReceiver.on (Z:\Docker\RingListener\node_modules\@eneris\push-receiver\dist\client.js:78:51)
    at PushReceiver.onReady (Z:\Docker\RingListener\node_modules\@eneris\push-receiver\dist\client.js:96:14)
    at Z:\Docker\RingListener\node_modules\@eneris\push-receiver\dist\client.js:127:34
    at new Promise (<anonymous>)
    at Timeout.connect [as _onTimeout] (Z:\Docker\RingListener\node_modules\@eneris\push-receiver\dist\client.js:126:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
```


### Screenshots

_No response_

### Additional context

Not sure, its correctly authenticating since I saw it fail with invalid refresh token when I first started, but I never see the refresh token update or get a new one, which makes me think its never actually listening to any events from Ring as I know the refresh tokens expires pretty fast once its used.

### OS

Windows, Docker

### Node.js Version

v18.14.1

### NPM Version

v9.5.0

### ring-client-api

v12.0.0

### Operating System

Docker