v3.1: tpu-client-next: set connection retry value to 1 for first retry (backport of #9581)

[mergify]

Problem

Fix bug with incorrect retry counter used for re-establishing connections.
This value is used like the follows:

                   ConnectionState::Retry(num_reconnects) => {
                        if *num_reconnects > self.max_reconnect_attempts {
                            error!(
                                "Failed to establish connection to {}: reached max reconnect \
                                 attempts",
                                self.peer
                            );
                            self.connection = ConnectionState::Closing;
                            continue;
                        }
                        sleep(RETRY_SLEEP_INTERVAL).await;
                        self.reconnect(*num_reconnects).await;
                    }

So if max_reconnect_attempts == 0 we get 0 > 0 and try reconnecting, which is not what expected.

Summary of Changes

---

This is an automatic backport of pull request #9581 done by [Mergify](https://mergify.com).

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 83.2%. Comparing base (7abb6df) to head (6854f72).

Additional details and impacted files

@@            Coverage Diff            @@
##             v3.1    #9616     +/-   ##
=========================================
- Coverage    83.2%    83.2%   -0.1%     
=========================================
  Files         865      865             
  Lines      376059   376059             
=========================================
- Hits       313072   313071      -1     
- Misses      62987    62988      +1     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.