[MrGhost23]

Summary

Fixes #246: a JS-created socket can reuse the id of a live accepted socket. The native connect()/listen() then fails for that id, and the error destroys the live accepted connection.

JS numbers sockets from 0 (src/Globals.js), while natively accepted sockets are numbered 5000 + n on iOS and (1 + serverId) * 1000 + n on Android. Nothing keeps the ranges apart, so once an app has created enough sockets in one session, they collide.

Changes

Natively accepted sockets now get negative ids (-1, -2, …) from a single counter per platform:

• iOS (TcpSockets.m): getNextId returns -(++_counter). The COUNTER_OFFSET define is removed.
• Android (TcpSocketServer.java): replaced the per-server (1 + serverId) * 1000 range with one shared AtomicInteger, returning -incrementAndGet().

JS ids start at 0 and only grow, so they can never be negative and the two id spaces can't overlap. On Android, two servers also stop sharing overlapping ranges. Using an AtomicInteger keeps id assignment safe across the listen threads.

Compatibility

• Ids are internal (Socket._id) and only compared for equality, never ordered or range-checked. I checked src/, ios/ and android/.
• Accepted-socket ids were never documented, so this is a fix, not a breaking change.
• iOS uses the id as the GCDAsyncSocket read tag (long), which accepts negative values.

Notes

• I couldn't build the native projects in my environment, so the change is deliberately minimal and type-safe on both sides. A run of the reproduction from Socket id collision: a new JS socket can reuse a live accepted socket's id, which then gets destroyed #246 on each platform would be appreciated.
• I hit this on iOS in production: an accepted socket received this client's socket is already connected after about a day of uptime, at the moment the app opened a new client socket.
• Prepared with AI assistance and reviewed by me.

Test plan

• With the reproduction from Socket id collision: a new JS socket can reuse a live accepted socket's id, which then gets destroyed #246, the long-lived accepted connection survives past 5000 (iOS) / 1000 (Android) client sockets
• connection events still deliver working sockets (data, write, close) with negative ids
• Multiple servers on Android accept connections without id overlap
• TLS servers (secureConnection) still work

Closes #246