peek() discards entries whose deadline has passed before returning the head of
the queue, and counted them with a bare registerRejectedFrame(). That is the
fourth drop path; the reported split covers three. The frames landed in the
total and in neither bucket, so `uavcan status` printed lines like
TX rejected: 64 frames (0 expired, 0 no memory)
which reads as "no drops worth caring about" when 64 frames of in-flight
transfers had just been discarded. Serving a DroneCAN node firmware update hits
this path on every interface.
The total stays a separate counter rather than the sum of the two buckets: it is
what makes an unclassified path visible at all, which is how this one was found.
(cherry picked from commit c2cf9be6aa)
Assisted-by: GitHub Copilot:gpt-6-astra
Backport-note: Companion to #28395: account for expired frames in the new TX-drop diagnostics.