quic: fixing stateless reset (again)

[jasnell]

The update to ngtcp2-25 appears to have broken the association of the
initial stateless reset token and the server's initial CID.

See: ngtcp2/ngtcp2#213

We can see the failure in the debug output:

QuicSession Client (zzz, 15) Receiving QUIC packet.
QuicSession Client (zzz, 15) Processing received packet
QuicSession Client (zzz, 15) Receiving 683 bytes of crypto data.
QuicSession Client (zzz, 15) Received secrets for app crypto level
QuicSession Client (zzz, 15) Updating connection ID dc90c8b81dce2649a79ef3a8909b7a9eb9bf6c8f (has reset token? No)
QuicSession Client (zzz, 15) Initializing application handler for ALPN zzz
QuicSession Client (zzz, 15) Default QUIC Application Initialized
QuicSession Client (zzz, 15) Writing 36 bytes of handshake handshake data.
QuicSession Client (zzz, 15) Sending pending data after processing packet
QuicSession Client (zzz, 15) Serializing session packets
QuicSession Client (zzz, 15) Handshake is completed. Remote Transport Params:
  Ack Delay Exponent: 3
  Active Connection ID Limit: 2
  Disable Active Migration: No
  Initial Max Data: 1048576
  Initial Max Stream Data Bidi Local: 262144
  Initial Max Stream Data Bidi Remote: 262144
  Initial Max Stream Data Uni: 262144
  Initial Max Streams Bidi: 100
  Initial Max Streams Uni: 3
  Max Ack Delay: 25000000
  Max Idle Timeout: 10000000000
  Max Packet Size: 65527
  Original Connection ID: N/A
  Preferred Address Present: No
  Stateless Reset Token: 2f39a010f89d95a95f35a9d00c39d862

The line QuicSession Client (zzz, 15) Updating connection ID dc90c8b81dce2649a79ef3a8909b7a9eb9bf6c8f (has reset token? No) reports that there is no stateless reset token associated with the initial CID but the server provided transport params does include the reset token (Stateless Reset Token: 2f39a010f89d95a95f35a9d00c39d862)

This is a work in progress until that is fixed

[jasnell]

PR to fix upstream: ngtcp2/ngtcp2#214

[jasnell]

Upstream fix landed, PR rebased and ready to go!

[jasnell]

Landed