feat: expose connectError event with HTTP status for transport override support

[idoros]

This PR exposes connection error information for ws-client-host through a new connectError event.

Changes in this PR:

• Add a connectError event to the WsClientHost that reports a status number
• Updates the connect_error handler from once to on, allowing multiple error events to be emitted during connection retries
• Reorders socketServerOptions in launchEngineHttpServer so they are applied after transports, enabling them to override transport defaults

Note that these changes do not modify the default transports configuration. As a result, the currently reported connection error status will be 0. To surface a meaningful status code, Socket.IO must prioritize polling over websocket, ensuring the connection begins with polling before upgrading to WebSocket.

[barak007]

test?

[idoros]

test?

there is no infra to check actual socket behavior and cause connection errors