TODO: Implement stateless reset

[jasnell]

Stateless reset support is going to be a bit tricky. An endpoint sends a stateless reset when it does not have access to connection state any longer, but that means we need to keep track of CIDs and their correspnding stateless reset tokens in a way that can survive a crash (which is ironic to say the least). Need to figure out how to implement this protocol feature.

[jasnell]

Currently, stateless reset tokens are generated randomly and not stored, which makes them useless for the intended purpose. In the future, we'll want to go with an alternative approach that allows stateless generation and subsequent verification of reset tokens. This can work in a number of ways but following the pattern of retry token generation would seem to make sense.