Handle `Receive query error`

[Chase Granberry]

Based on: riverqueue/river#238 (comment)

I was able to reproduce locally with the linked repo: https://github.com/JanRuettinger/river_issue/tree/main

We are getting:

ClientHandler: Receive query error: {:error, {:invalid_msg, {:tls_alert, {:bad_record_mac, 'TLS server: In state connection at tls_record_1_3.erl:351 generated SERVER ALERT: Fatal - Bad Record MAC\n decryption_failed'}}}}

Which I suspect is leaving stray connections open which eventually eats up the connection pool?