fix(ws): Land a sounding on the ack that asks for it, not on the next check
A queue the sounding reads under content (content probing past the cap,
or taking the padding's place) was cut at the steer's next check, up to
half a second later, and the stream ran its whole overshoot into the
queue meanwhile: a content probe that found a link grown from 4 to
10 Mbit/s had reached 15.4 and aged the picture 484 ms in two runs of
four. The drain's reading likewise waited a check to lift the
provisional target.
The ack that judges such a queue (the first after the detector fired),
the one that ends a hold content filled, and the one that ends a drain
now ask for the landing (Sounding::land_due), and the socket's handler
lands the steer at once (WsService::land_sounding). A padded hold still
lands on the check, after reading the path for its whole span.