[Bug] Dubbo 3.2.11 work with Istio get no provider, connection error

### Pre-check

- [X] I am sure that all the content I provide is in English.

### Search before asking

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

### Apache Dubbo Component

Java SDK (apache/dubbo)

### Dubbo Version

Dubbo 3.2.11

### Steps to reproduce this issue

Use triple call provider api with istio sidecar injection, after about 1-2 hours, get RPC error, the log shows no provider problem.

By troubleshooting, we found the problem may be netty get the wrong connection status, the connection is health, but netty mark it as bad, so the RPC has been terminated.

### What you expected to happen

Work fine as it start.

### Anything else

_No response_

### Are you willing to submit a pull request to fix on your own?

- [ ] Yes I am willing to submit a pull request on my own!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

Start by reproducing the Dubbo 3.2.11 Java SDK triple call with Istio sidecar injection and observe the failure after 1–2 hours. Inspect the Netty connection-status handling and logs; done means healthy connections remain usable and RPC calls no longer terminate with a no-provider error.

Written by the indexing model from the issue text.