Fixes to avoid operator conflict with the sentinel in choosing master

[dinesh-murugiah]

Fixes # .

Changes proposed on the PR:

• Currently Operator and Sentinel seems to share similar responsibility in certain conditions ,

• this will create conflict and eventually misconfigure the system

• For Example:

• When a master is not available and sentinel is in the process of taking an action to fix a replica as master,

• at the same time if the operator also fixes another replica as a slave , it could end up in a split brain or necessary switch of master between two replicas, moreover sentinel is the right candidate to choose master

• and operator should not step in unless sentinel is in a good shape to do its job

• The Role of the operator is primarily during initial/First deployments of redis-failover

• and also in scenarios where sentinel cannot make a decision

[samof76]

Great, looks good. @ese please review.

[ese]

Thanks! I think is more reliable way to ensure redis-operator acts when it have to do. Since GetMinimumRedisPodTime is no longer used we should remove it.