Fix TCP reconnect after close and run connected messaging in CI

TCPLayer.sendNextMessage reconnected unconditionally whenever the
state was disconnected, so any deferred wakeup arriving after close()
(e.g. from the final write's callback) silently opened a fresh socket
that nothing would ever close. It now reconnects only when the request
queue is non-empty.

Adds the OpENer connected-messaging integration test to CI.

https://claude.ai/code/session_01AuAYuP6dTn8ALpkKErQuby

Author: claude

.github/workflows/ci.yml

@@ -48,6 +48,9 @@ jobs:
     - working-directory: node-drivers
       run: node test/integration/eip.js
 
+    - working-directory: node-drivers
+      run: node test/integration/cip-connected.js
+
     - uses: actions/setup-python@v5
       with:
         python-version: '3.11'

src/layers/tcp/index.js

@@ -240,8 +240,11 @@ export default class TCPLayer extends Layer {
         });
       }
     } else if (this._connectionState === 0) {
-      /** Reconnect */
-      connect(this);
+      /** Reconnect only when there is something to send, otherwise a
+       * deferred wakeup after close() would reopen the connection */
+      if (this.hasRequest()) {
+        connect(this);
+      }
     }
   }