Intercom: unlock function returns 404
### Is there an existing issue for this?

- [X] I have searched the existing issues

### Describe The Bug

Since a couple days ago, the [unlock function ](https://github.com/dgreif/ring/blob/main/packages/ring-client-api/ring-intercom.ts#L70) is returning the following error:
```
HTTPError: Response code 404 (Not Found)
    at Request.<anonymous> (/usr/src/app/node_modules/got/dist/source/as-promise/index.js:118:42)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 'ERR_NON_2XX_3XX_RESPONSE',
  timings: {
    start: 1696329795541,
    socket: 1696329795542,
    lookup: 1696329795545,
    connect: 1696329795563,
    secureConnect: 1696329795784,
    upload: 1696329795785,
    response: 1696329795958,
    end: 1696329795962,
    error: undefined,
    abort: undefined,
    phases: {
      wait: 1,
      dns: 3,
      tcp: 18,
      tls: 221,
      request: 1,
      firstByte: 173,
      download: 4,
      total: 421
    }
  }
}
```

I first noticed the problem when it logged me out for some reason (I was getting `Error: Refresh token is not valid.  Unable to authenticate with Ring servers.`).
I performed the auth flow again, now I can successfully read the battery level with `intercom.batteryLevel`, but calling `intercom.unlock()` returns that 404.

I'm not sure how to discover the new URL, if it changed on Ring's side.

### To Reproduce

_No response_

### Expected behavior

It should unlock the door.

### Relevant log output

_No response_

### Screenshots

_No response_

### Additional context

_No response_

### OS

Linux (node:18-alpine docker image)

### Node.js Version

v18.7.0

### NPM Version

8.15.0

### ring-client-api

12.0.1

### Operating System

Linux (node:18-alpine docker image)