fix: add catch for get conn exception (#13)

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Improvements**
* Enhanced connection timeout handling with diagnostic logging.
Connections are now properly released during timeout scenarios to
prevent resource leaks and improve visibility into connection issues.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Author: killagu

package.json

@@ -18,7 +18,8 @@
   },
   "dependencies": {
     "mysql2": "^3.9.1",
-    "sqlstring": "^2.3.3"
+    "sqlstring": "^2.3.3",
+    "onelogger": "^1.0.0"
   },
   "devDependencies": {
     "@eggjs/tsconfig": "^1.3.2",

src/client.ts

@@ -3,6 +3,7 @@ import { promisify } from 'node:util';
 import { setTimeout } from 'node:timers/promises';
 import mysql, { Pool } from 'mysql2';
 import type { PoolOptions } from 'mysql2';
+import { getLogger } from 'onelogger';
 import type { PoolConnectionPromisify, RDSClientOptions, TransactionContext, TransactionScope } from './types';
 import { Operator } from './operator';
 import { RDSConnection } from './connection';
@@ -167,6 +168,10 @@ export class RDSClient extends Operator {
     if (typeof connOrTimeout === 'number') {
       connPromise.then(conn => {
         conn.release();
+      }).catch(e => {
+        const logger = getLogger();
+        e.message = 'get conn failed after timeout: ' + e.message;
+        logger.warn(e);
       });
       throw new PoolWaitTimeoutError(`get connection timeout after ${connOrTimeout}ms`);
     }