GetDevices hangs on M1 Mac
<!--
Please DO NOT DELETE THIS TEMPLATE or your issue may be closed immediately.
Before opening an issue, search for open and closed GitHub issues that match your situation.

If this is a Live Stream issue please go back and use the Live Streaming issue template.
-->

# Bug Report

### Describe the Bug
When running the ring-client-api on M1 Mac, the client appears to hang on the getDevices call (sample program below). I realize my environment is not common, and would be happy to help debug as needed.

### To Reproduce

I first saw this issue when running homebridge, then was able to reproduce in a standalone script. Note that I am not a Node js developer so the code below is rough:

Script:
```
import  { RingApi }  from '/opt/homebrew/Cellar/node/15.5.0/node_modules/ring-client-api/lib/api/api.js';

const ringApi = new RingApi({
  refreshToken: 'ABC123',
	debug: true

});
console.log('Initialized Ring API');
const locations =  await ringApi.getLocations();
const allCameras = await ringApi.getCameras()

console.log(
    `Found ${locations.length} location(s) with ${allCameras.length} camera(s).`
)

const    location = locations[0];
//location is logged properly
console.log(location);
const devices = await location.getDevices()
//Code never makes it here
console.log('Got Devices');
```


From stepping into the code, the following area of ring-client-api location.js is what appears to never return:
```
return new Promise((resolve, reject) => {
                connection.once('connect', () => {
                    resolve(connection);
                    this.onConnected.next(true);
                    util_1.logInfo('Ring connected to socket.io server');
                    assets.forEach((asset) => this.requestList(deviceListMessageType, asset.uuid));
                });
                connection.once('error', reject);
            }).catch(reconnect);
```

### Expected behavior
Expect the list of devices to be returned

### Screenshots/Logs
NA

### Additional context
I have homebridge-ring running fine on a Raspberry Pi, so I don't feel this is specific to my network

### Environment
I installed node/npm using the ARM HomeBrew build for the M1 Mac.
 - OS: MacOS 11.1
 - Node.js: 15.5.0
 - NPM: 7.3.0
 - ring-client-api: 9.12.8
