kafka(ticdc): sarama admin client fetch metadata by cache (#9511)

[ti-chi-bot]

This is an automated cherry-pick of #9511

What problem does this PR solve?

Issue Number: close #9504

What is changed and how it works?

1. Improve the robustness of the Kafka admin client when the network is unstable by adjusting the following configuration settings:

config.Metadata.Retry.Max = 10 # Maximum number of retries when the admin client is getting metadata.
config.Metadata.Retry.Backoff = 200 * time.Millisecond # Retry backoff time when encountering a retryable error.
config.Metadata.Timeout = 2 * time.Minute # Maximum total retry time when the admin client is getting metadata.

config.Admin.Retry.Max = 10
config.Admin.Retry.Backoff = 200 * time.Millisecond
config.Admin.Timeout = 10 * time.Second

1. The queryWithRetry method has been removed. Instead, when an unretryable error is encountered, the error will be returned as soon as possible. This allows sinkManager to reset the entire client and prevents the admin client from getting stuck in a retry loop if it encounters a unretryable network error.

Check List

Tests

• Unit test
• Manual test (add detailed scripts or steps below)

Questions

Will it cause performance regression or break compatibility?

Do you need to update user documentation, design documentation or monitoring documentation?

Release note

`None`

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: asddongmen, nongfushanquan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [asddongmen]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment