CORTX-32842: Support multiple cortx-control pods

Description

This change provides support for multiple cortx-control pods in a cluster. This is supported in helm value: control.replicaCount. There is no support in solution.yaml for this at this time.

Type of change

[ ] Bug fix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds new functionality)
[ ] Breaking change (bug fix or new feature that breaks existing functionality)
[ ] Third-party dependency update
[ ] Documentation additions or improvements
[ ] Code quality improvements to existing code or test additions/updates

Applicable issues

This change fixes an issue: CORTX-32842

CORTX image version requirements

N/A

How was this tested?

Deploy with 1 pod, 3 pods, 10 pods
Verify that all cortx-control pods are serving data
Verify that all cortx-control pods are in sync (all accept write requests, all return same GET responses)
Run basic k8s deploy regression test.

Additional information

There may be issues with running multiple cortx-control pods in terms of the implementation of those containers. I have done basic functional test, but I leave it to the team responsible for cortx-control implementation to do due diligence in developer test.

Checklist

[x] The change is tested and works locally.
[ ] New or changed settings in the solution YAML are documented clearly in the README.md file.
[x] All commits are signed off and are in agreement with the CORTX Community DCO and CLA policy.

If this change requires newer CORTX or third party image versions:

[ ] The image fields in solution.example.yaml have been updated to use the required versions.
[ ] The appVersion field of the Helm chart has been updated to use the new CORTX version.

If this change addresses a CORTX Jira issue:

[x] The title of the PR starts with the issue ID (e.g. CORTX-XXXXX:)

Seagate / cortx-k8s