golang-custom-raft: maximum_lag_on_failover doesn't work as it should

[doodles526]

maximum_lag_on_failover incorrectly tries to query an existing leader for the WAL position. Problem is, the time which maximum_lag_on_failover should be checked - a leader wouldn't exist. Solution would be to implement historic information on members