operator: make an infinity retry for connecting to store

[YuJuncen]

What problem does this PR solve?

Issue Number: close #52175

Problem Summary:
See the issue.

What changed and how does it work?

This make an infinity retry for the connecting to store phase.
The retry of waiting apply phase has been kept because it seems waiting apply isn't always lasting for minutes.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @YuJuncen. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[codecov]

Codecov Report

Merging #52177 (b877357) into master (9ad0862) will increase coverage by 0.2089%.
Report is 1 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #52177        +/-   ##
================================================
+ Coverage   74.1468%   74.3557%   +0.2089%     
================================================
  Files          1467       1467                
  Lines        354142     426731     +72589     
================================================
+ Hits         262585     317299     +54714     
- Misses        72388      89635     +17247     
- Partials      19169      19797       +628     

Flag	Coverage Δ
integration	48.9581% <62.5000%> (?)
unit	71.0171% <100.0000%> (-1.8875%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9957% <ø> (-2.3014%)	⬇️
parser	∅ <ø> (∅)
br	49.3621% <100.0000%> (+7.2110%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BornChanger, Leavrth

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:

• br/OWNERS [BornChanger,Leavrth]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-03-28 05:37:39.782061316 +0000 UTC m=+2132686.804307697: ☑️ agreed by Leavrth.
• 2024-04-03 04:50:18.79377909 +0000 UTC m=+419480.321319636: ☑️ agreed by BornChanger.

[BornChanger]

/label needs-cherry-pick-release-6.5

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #52360.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #52560.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #52561.