Description of problem:

Currently OVS Raft cluster initialize with the default election-timer (1000ms). If user wants to change the election-timer value to initialize the cluster with specific value, they need to manually find the raft leader and increase the value by 2*default_value using ovs-appctl till they reach the timer value they want to set.
This requires consumers to write some operational code around it to set this value (for example, see pathc [1]). This can get tricky specifially if your cluster start partitioning during the start-up because of the heavy load to start with.

By allowing this value to be set at start-up of the raft cluster, would simplify the start-up process for the consumers (CNO, OVN, OVN-Kubernetes).


Expected results:
User should be able to pass election-timer value using a start-up time config knob (e.g --election-timer <value>), and raft cluster will override that value as a default election-timer.

[1] https://github.com/openshift/cluster-network-operator/pull/615/commits/bd5f5e6ebd594d1d510b9002f02163844c94ed1d#diff-54b09156f80dfb820afa115de13b8f32R166