Event triggered on Connection State Recovery Expiration

Is your feature request related to a problem? Please describe.

Per-connection, we're keeping a large object in memory, which we would prefer to use across connections that are recovered through connection-state-recovery. Connection state recovery solves one problem for us, in that we can reconnect a client to its object, but this makes it harder to know when to delete the object.

Describe the solution you'd like

When a connection exceeds the connection state recovery maxDisconnectionDuration, I'd like an event trigger with the SocketID as an argument.

Describe alternatives you've considered

We've considered setting an additional timeout, but this won't ever be as accurate - we'd have to make this timeout longer than maxDisconnectionDuration, and deal with our large staying around longer than needed.

The issue names no files or tests. Start by locating the connection-state-recovery handling for maxDisconnectionDuration and trace how expiration is detected; done means an event is emitted with the expired connection's SocketID at that point, with coverage for the event payload and timing.