[Bug] Is there any graceful way to prevent running out of http2 stream id in Dubbo3.x

### 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.x

### Steps to reproduce this issue

Based on the discussion in #13731, I think it is an improper way to make a reconnection triggered by GoAwayFrame(stream id exhausted) cause there will be 100% request failure before the new connection being active and it is unacceptable for production scenario. To make sure the connection is consistently available, is it possible to make a new connection before the stream id is about to be exhausted?

### What you expected to happen

1. Make a new connection before the stream id is about to be exhausted.

### Anything else

_No response_

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

- [X] 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 with the discussion in issue #13731 and reproduce the Dubbo 3.x HTTP/2 behavior around GoAwayFrame stream ID exhaustion. Trace the connection activation and reconnection behavior, then verify that a new connection becomes available before exhaustion without causing request failures during the transition.

Written by the indexing model from the issue text.