[Haihan-Jiang]

Change Description

Fixes #576.

CloudSQLInstance.close() still destroys every tracked socket so shutdown can clean up active handles, but it no longer passes a synthetic CloudSQLConnectorError into socket.destroy(). Passing that error causes Node to emit an asynchronous socket error event; after drivers such as pg have drained a pool and removed socket listeners, that event can become an uncaught exception during intentional connector shutdown.

The added unit test verifies close-time socket teardown calls destroy() without an error argument.

Checklist

• Make sure to open an issue as a bug/issue before writing your code
• Ensure the tests and linter pass
• Appropriate documentation is updated (not necessary)

Validation

• npx tap -t0 -c test/cloud-sql-instance.ts
• npm run lint
• npm run compile
• npm test

[Haihan-Jiang]

This is ready for review from my side. The remaining integration-test-pr checks appear to require project-side approval/run permissions; could someone take a look or trigger them when convenient?

[Haihan-Jiang]

I rebased this on the latest main and resolved the conflict in src/cloud-sql-instance.ts.

I kept the close path from passing a synthetic error into socket.destroy(), and updated the unit test setup to use a domain-backed instance so the tracked-socket path is exercised.

Validation:

• npm test -- test/cloud-sql-instance.ts
• npm run compile
• npm run lint

The latest head is 42bf85b; GitHub shows the commit signature as valid.