Duplicate RETIRE_CONNECTION_ID frame leads to connection close with PROTOCOL VIOLATION

I encountered an issue while using quiche as QUIC client to contact a quic-go server.
If the server retires the same connection ID twice and no more than one connection ID is available, quiche closes the connection with a protocol violation error.

Attached is a pcap file demonstrating the described behavior.
The duplicate `RETIRE_CONNECTION_ID` frames are in Wireshark No. 17 and 18.
`CONNECTION_CLOSE` is in the next packet (No. 19).

**Expected behavior:**
The client should not close the connection.
Instead, it should first verify if the `RETIRE_CONNECTION_ID` frame references an active connection ID. If it does, the client should then check whether the connection must be closed due to no other connection IDs being available after retirement.

Receiving the same RETIRE_CONNECTION_ID frame multiple times is expected behavior according to RFC9000:
> New connection IDs are sent in NEW_CONNECTION_ID frames and retransmitted if the packet containing them is lost. Retransmissions of this frame carry the same sequence number value. **Likewise, retired connection IDs are sent in RETIRE_CONNECTION_ID frames and retransmitted if the packet containing them is lost.**

I think the respective code is here:
https://github.com/cloudflare/quiche/blob/0ba4a7484c3d52b93609ebf6bdc57c33c098cbc6/quiche/src/cid.rs#L193-L202

The issue seems to be that `inner.len()` is checked before verifying that the contained sequence number is actually in the list.

[quiche-client-duplicate-retire-connection-id.pcapng.gz](https://github.com/user-attachments/files/16677769/quiche-client-duplicate-retire-connection-id.pcapng.gz)