Heartbeat timeout message does not show when using native kTLS

[lukas8219]

Describe the bug
The Heartbeat timeout log does not show up when using kTLS.

Describe your setup
Two connections in CloudAMQP - 20s heartbeat. One plain, one TLS. Newer LavinMQ Version with Ubuntu26

How to reproduce

• Let both connections run in a blocked environment. We used Pika.

>>> urlB='amqp://nzcidpnq:PWD@test-windy-cattle.lmq.cloudamqp.com/nzcidpnq?heartbeat=20'
>>> urlA='amqps://nzcidpnq:PWD@test-windy-cattle.lmq.cloudamqp.com/nzcidpnq?heartbeat=20'
>>>
>>>
>>> connA=openConn(urlA)
>>> connB=openConn(urlB)
>>>
>>> chA=connA.channel()
>>> chB=connB.channel()

Both connections closed as expected by missing heartbeats, but the kTLS one closed in silence

Expected behavior
Log Heartbeat timeout shows up

** Root Cause **
There's a branch with a validated fix. The branch has AI generated code with much more than necessary.
The fix is to handle the new OpenSSL read timeout. The kTLS binding does not throw an error.

[carlhoerberg]

I think that should be reported to https://github.com/crystal-lang/crystal/ as it sounds like a stdlib bug

[lukas8219]

@carlhoerberg But should we fix it for now? In the std/lib monkey patch?