Enable backup Unisphere

[baoy1]

Description

Previously backup U4P URL is only used when building connection, and backup U4P connection will not be saved if primary URL is working. Considering primary URL will stop working somehow, we cannot get valid connection.
So we need to save backup connection if primary U4P stop working.

GitHub Issues

List the GitHub issues impacted by this PR:

GitHub Issue #
dell/csm#586

Checklist:

• I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
• I have verified that new and existing unit tests pass locally with my changes
• I have not allowed coverage numbers to degenerate
• I have maintained at least 90% code coverage
• I have inspected the Grafana dashboards to verify the data is displayed properly
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• I have maintained backward compatibility

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

• make check test

➜  csm-metrics-powermax git:(feature-586-enable_backup_u4p_probe) make check test
./scripts/check.sh ./cmd/... ./opentelemetry/... ./internal/...
=== Checking format...
=== Finished
=== Vetting...
=== Finished
=== Linting...
=== Finished
=== Running gosec...
=== Finished
go test -count=1 -cover -race -timeout 30s -short `go list ./... | grep -v mock`
?       github.com/dell/csm-metrics-powermax/cmd/metrics-powermax       [no test files]
ok      github.com/dell/csm-metrics-powermax/internal/common    0.401s  coverage: 92.3% of statements
ok      github.com/dell/csm-metrics-powermax/internal/entrypoint        1.528s  coverage: 93.4% of statements
ok      github.com/dell/csm-metrics-powermax/internal/k8s       0.129s  coverage: 94.3% of statements
?       github.com/dell/csm-metrics-powermax/internal/k8sutils  [no test files]
?       github.com/dell/csm-metrics-powermax/internal/reverseproxy/common       [no test files]
ok      github.com/dell/csm-metrics-powermax/internal/reverseproxy/config       0.324s  coverage: 91.2% of statements
?       github.com/dell/csm-metrics-powermax/internal/reverseproxy/utils        [no test files]
ok      github.com/dell/csm-metrics-powermax/internal/service   0.089s  coverage: 100.0% of statements
ok      github.com/dell/csm-metrics-powermax/internal/service/metric    0.139s  coverage: 94.8% of statements
?       github.com/dell/csm-metrics-powermax/internal/service/types     [no test files]
?       github.com/dell/csm-metrics-powermax/opentelemetry/exporters    [no test files]
ok      github.com/dell/csm-metrics-powermax/utils      0.036s  coverage: 100.0% of statements

Manual inspection of the GUI

I have verified that the dashboards show the data properly while generating I/O and storage resources

• Yes
• No

[baoy1]

run e2e test

[taohe1012]

no place to set config.LivenessProbeTickInterval, so why livenessProbeTickInterval := config.LivenessProbeTickInterval

[baoy1]

It is for test case purpose.

[baoy1]

run e2e test

[baoy1]

run e2e test

[baoy1]

run e2e test