Telemetry wrongly assumes the connection is in a disconnected state

[starbelly]

Currently a lot of places where a telemetry call is made assumes the state of the connection is disconnected.

Example :

elixir-mllp/lib/mllp/sender.ex

Line 333 in cd0dc88

%{status: :disconnected, error: error, context: "send message failure"},

The fact is we simply don't know if that's true. We could have a better idea if we checked a lot of error codes, but without doing that, we can't assume we're disconnected.

It may be we might be in a better position as far as avoiding error code checking to deduce the status of the socket if we made use of {:active, :once} on in the client, even still there will be cases where we won't be sure unless we poll the socket (i.e., try to perform a read and see what we get).