tungstenite 0.17.x has an open RUSTSEC advisory

[eric-seppanen]

Describe the bug
The tungstenite dependency has an open RUSTSEC advisory.

To Reproduce
Running cargo deny show advisories on a crate including rerun will display:

     = ID: RUSTSEC-2023-0065
     = Advisory: https://rustsec.org/advisories/RUSTSEC-2023-0065
     = The Tungstenite crate through 0.20.0 for Rust allows remote attackers to cause
       a denial of service (minutes of CPU consumption) via an excessive length of an
       HTTP header in a client handshake. The length affects both how many times a parse
       is attempted (e.g., thousands of times) and the average amount of data for each
       parse attempt (e.g., millions of bytes).
     = Announcement: https://github.com/snapview/tungstenite-rs/issues/376
     = Solution: Upgrade to >=0.20.1 (try `cargo update -p tungstenite`)
     = tungstenite v0.17.3
       ├── re_ws_comms v0.12.1
       │   ├── re_data_source v0.12.1
       │   │   └── rerun v0.12.1
       │   │       └── my_crate v0.1.0
       │   ├── re_sdk v0.12.1
       │   │   └── rerun v0.12.1 (*)
       │   └── rerun v0.12.1 (*)
       └── tokio-tungstenite v0.17.2
           └── re_ws_comms v0.12.1 (*)

Expected behavior
Dependencies should be clean of open advisories. Even if it's unlikely for the tungstenite issue to cause problems with rerun, it's still a time-consuming issue for downstream users that run automated advisory checks.