fix: socket write error should not result in a crash report

[zmstone]

When socket is closed writing data to it would result in a einval error.
In this case the tcp_closed and ssl_closed message are likely already in the mailbox,
this should not result in a crash report, so change it to a {shutdown, _} reason instead.

e.g. from proc_lib:crash_report/4:

error_logger: {"type":"crash_report","tag":"error_report"}, logger_formatter: {"title":"CRASH REPORT"}, msg: crasher: initial call: kpro_connection:init/4, pid: <0.12144989.0>, registered_name: [], exit: {{send_error,[{api,produce},{vsn,7},{caller,<0.1983516.0>},{reason,einval}]}