Improve cluster cant failover log conditions

[enjoy-binbin]

This PR adjusts the logging conditions of clusterLogCantFailover
in this two ways.

1. For the same cant_failover_reason, we will print the log once
   in CLUSTER_CANT_FAILOVER_RELOG_PERIOD, but its value is 10s, which
   is a bit long, shorten it to 1s, so we can better track its state.
   We get to see the system making progress by watching the message.
   Using 1s also covers pretty much all cases as i don't see a reason
   for using a <1s node timeout, test or prod.

2. We will not print logs before the nolog_fail_time, its value
   is cluster-node-timeout+5000. This may casue us to lose some logs,
   for example, if cluster-node-timeout is small, auth_timeout will
   be 2000, and auth_retry_time will be 4000. In this case, we will
   lose all the reasons during the election if the failover is timedout.
   So remove the nolog_fail_time logic, since we still do have the
   CLUSTER_CANT_FAILOVER_RELOG_PERIOD logic, we won't print too many
   logs.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.05%. Comparing base (a4ee8da) to head (9e050f8).
Report is 72 commits behind head on unstable.

Additional details and impacted files

@@             Coverage Diff              @@
##           unstable     #780      +/-   ##
============================================
+ Coverage     70.04%   70.05%   +0.01%     
============================================
  Files           112      112              
  Lines         60602    60587      -15     
============================================
- Hits          42447    42445       -2     
+ Misses        18155    18142      -13     

Files	Coverage Δ
src/cluster_legacy.c	85.97% <ø> (+0.18%)	⬆️

... and 15 files with indirect coverage changes