Missing heart beat closing does not raise the correct notification #362
Description
Describe the bug
The close notification is incorrect when the client is closed due to a missing heartbeat.
So the client can't be reconnected. The client should consider the missing heartbeat as an error.
Reproduction steps
It should be enough to do the same: rabbitmq/rabbitmq-stream-dotnet-client#393
Expected behavior
Raise the socket closed error so the client can reconnect.
Additional context
No response