Create timeout and onidle clients

[Bolodya1997]

Issue

Currently we have timeout for the initial Request, but we don't have any timeout for the retries to reestablishing the existing Connection. Imagine such case:

1. NSC requests NSM for some service.
2. NSM provides such service.
3. Some time goes.
4. NSM starts failing to provide such service.
5. NSC starts requesting service again in infinite loop ([qfix] Add refresh retries on failure #1081 (comment)).

Possible solution

We can create timeout and completed client chain elements:

1. timeout - just the same as a server timeout chain element, but it has some internal timeout instead of Conn.GetPrevPathSegment() expiration time.
2. onidle - just the same as a server onidle chain element.

In such case client will close all failed Connections on some timeout and after close itself.

[Bolodya1997]

@edwarnicke @denis-tingaikin
cc

[denis-tingaikin]

Can we just use attempts for refresh?

[Bolodya1997]

Can we just use attempts for refresh?

We can use it instead of timeout, not instead of onidle.
I suppose that having 30 seconds timeout is more clear and predictable than 10 times refresh attempts.

[edwarnicke]

@Bolodya1997 Could we simply not have the refresh loop check for expiration and terminate the loop locally if it is past expire?

[Bolodya1997]

@Bolodya1997 Could we simply not have the refresh loop check for expiration and terminate the loop locally if it is past expire?

Yes, it should be better.