[Enhancement] Socket Channel may be null if error or crash during `client-side` connecting

### Search before asking

- [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues.

### Enhancement Request

Locating at: org/apache/eventmesh/client/tcp/common/TcpClient.java
Line: 118

the implementation of `close()`

```java
try{
channel.disconnect().sync();
// ...
} catch {
// ...
}
```

`close()` would be called
- call func explicitly
- call func in `finally` block for resource safety
- deffer implicitly caz `try()`

socket will fail if the error or crash is on `bind()`, `channel` reference will be Null

### Describe the solution you'd like

Removing `channel.disconnect().sync(); `, resources will be closed with the determination of `EventLoopGroup`

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

Start in org/apache/eventmesh/client/tcp/common/TcpClient.java around line 118 and inspect how close() behaves when bind() fails before channel is initialized. Trace the resource-cleanup path through EventLoopGroup and verify that closing after a connection error or crash does not dereference a null channel and that resources are released.

Written by the indexing model from the issue text.