Ability to configure retry conditions for EgressIP heartbeat checks

1. Proposed title of this feature request
Ability to configure retry conditions for EgressIP heartbeat checks

2. What is the nature and description of the request?
A large APAC customer is requesting the ability to configure the EgressIP heartbeat checks (either timeout or retry counts) for OVN-Kubernetes.

There is packet loss in their environment resulting in EgressIPs migrating between Nodes regularly. They are working on resolving the packet loss, however as an additional mechanism to ensure stability in their environment, they would like the ability to influence the retry mechanisms for heartbeats of egress-assignable nodes in OVN Kubernetes

For additional context about the retry mechanism in question, see the following BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=2083425
https://github.com/ovn-org/ovn-kubernetes/pull/2996/commits

For additional information about the heartbeats:
https://github.com/ovn-org/ovn-kubernetes/blob/master/go-controller/pkg/ovn/egressip.go#L2101-L2108

3. Why does the customer need this? (List the business requirements here)
Customer is requesting this config so they can find the most resilient value(s) for their network.

4. List any affected packages or components.
OVN-Kubernetes