Push Receiver stops getting notifications
<!--
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
A long-running connection to the Ring API stops receiving notifications through the push receiver. Once the account is in this state, recycling the connection (or even the process) has no effect - the push receiver still receives no dings.

### To Reproduce
Steps to reproduce the behavior:
 - Create a RingApi and subscribe to notifications
 - Wait about 3 days
 - Trigger motion on a camera - eventually the dings will stop coming through to the API

### Expected behavior
Dings should come through forever.


### Screenshots/Logs

### Additional context
The only workaround I've found once in this state is to remove the Authorized Devices from the account and generate a fresh refresh token. Somehow it appears the token is getting "tainted" with Ring and not receiving push notifications any more. I'm _guessing_ this is something to do with the credentials for FCM not being updated correctly, but it's not clear to me what the issue here would be.

### Environment

 - OS: Alpine Linux
 - Node.js: 16.14.2
 - ring-client-api: v11
