feat(application): dissect every SSLv2 record in a TCP segment, not only the first #2567

From the 2026-11-01 conventions audit, re-verified on 73add05a3; follow-up from #2517. test-coverage.rst, "Round-Trip Invariants": a round trip reproduces its input exactly.

• feat(application): dissect every whole TLS record in a TCP segment (#2517) #2537 makes TLS chain each whole record in a TCP segment as the next layer. SSLv2 still dissects only the first: a CLIENT-HELLO followed by a second record parses as TCP:SSLv2:Raw (reproduced on 73add05a3 with SSLv2(first + second, ...), whose protochain is SSLv2:Raw). DTLS has the same gap, tracked in feat(application): dissect every DTLS record in a datagram, not only the first #2535.

Fix: chain each whole SSLv2 record as the next layer, as #2517 does for TLS, with byte-exact round trips (build -> parse -> rebuild). Then remove SSLv2 from the exception that protocol-family-grouping.rst, "Chained Records", records.
Blocked: builds on #2537's chaining and edits the page it adds; unblocks when #2537 merges (gh pr view 2537 --json state -q .state prints MERGED).