Emit a reconnectFailure event

[ggrossetie]

err can be undefined on fail event when retryBackoff.backoff is called without an error object:

TypeError: Cannot read properties of undefined (reading 'message')
    at Backoff.<anonymous> (/path/to/project/node_modules/pino-socket/lib/TcpConnection.js:221:100)
    at Backoff.emit (node:events:520:28)
    at Backoff.backoff (/path/to/project/node_modules/backoff/lib/backoff.js:42:14)
    at reconnect (/path/to/project/node_modules/pino-socket/lib/TcpConnection.js:134:18)
    at Socket.closeListener (/path/to/project/node_modules/pino-socket/lib/TcpConnection.js:147:7)
    at Socket.emit (node:events:520:28)
    at TCP.<anonymous> (node:net:687:12)

[ggrossetie]

@mcollina I'm thinking about it because it's a breaking change, do you think we should reconnect if the socket was closed (or ended) without an error?

[mcollina]

no we shouldn't reconnect.

[ggrossetie]

done!
I've also added a test to make sure that a close event is sent on the stream when the socket is gracefully closed using socket.destroy() (without an error)

[mcollina]

lgtm