hubble/relay: ignore backoff on direct connection requests
hubble/relay: ignore backoff on direct connection requests

On peer change notifications or call to
`pool.Manager.ReportOffline(name string)`, the backoff interval should
be ignored to re-attempt a connection. This change typically addresses
the following scenario:

  1. Node Foo is offline
  2. The connectivity checker attempts to reconnect several time; each
    time the backoff is increased.
  3. Node Foo becomes available; a peer change notification is received
  4. Oops, no connection attempt is made to Foo because of a large
     backoff duration

Signed-off-by: Robin Hahling <042b6757f29293f4affc22596084b908e3917891@gw-computing.net>

tgraf/cilium,cilium/cilium,cilium-team/cilium,michi-covalent/cilium,cilium-team/cilium,michi-covalent/cilium,tgraf/cilium,tklauser/cilium,michi-covalent/cilium,michi-covalent/cilium,tgraf/cilium,tklauser/cilium,tgraf/cilium,cilium/cilium,cilium/cilium,tklauser/cilium,tklauser/cilium,cilium/cilium,michi-covalent/cilium,tgraf/cilium,cilium/cilium,tklauser/cilium,tgraf/cilium