tlsReadLoop() is not awaited and has no .catch() — TLS read errors silently hang the pg client forever

Bug description

src/shims/net/index.ts line 645 starts tlsReadLoop() with a comment saying it's "deliberately NOT awaited", but provides no error handling:

// deliberately NOT awaited; runs in background
tlsReadLoop(); // ← no .catch()

If the TLS read loop rejects (e.g. mid-stream connection drop, unexpected EOF), the error becomes an unhandled promise rejection. The socket never emits 'error' or 'close', so the pg client hangs indefinitely — queries never time out, and the connection is never recycled by a pool.

tlsWrite() (same file, nearby) was fixed to handle errors. tlsReadLoop() has the same gap.

Fix

tlsReadLoop().catch((err) => {
  this.emit('error', err);
  this.emit('close');
});

Environment

• Verified against current main branch

Start in src/shims/net/index.ts around line 645 and compare the unawaited tlsReadLoop() with the nearby tlsWrite() error handling. Verify that a rejected TLS read emits both error and close so a dropped connection does not hang the pg client or its pool.