Adding timeout overrides to NodeConnectionManager methods

[tegefaulkes]

Specification

While we can specify the timeouts when creating a NodeConnectionManager there are cases where we want to be able to specify a timeout when creating a connection.

For this we will need to add an optional connConnectTime parameter to any NodeConnectionManager method that can create a connection. this ill override the timeout of trying to create a connection if set.

Additional context

• Relates Investigate means of authenticating a node ID when adding to NodeGraph #322 needs this to avoid blocking for a long time when checking a node.

Tasks

1. Add optional timeouts to all of the NodeConnectionManager methods that could create a new connection.

[tegefaulkes]

Didn't really need an issue for this since it's a small change. But it leaves a paper trail for discussion.

I'm in the process of adding the timeout to the methods such as createConnection, establishNodeConnection , withF and withG being the main ones. Do we want to add optional timeouts for getClosestGlobalNodes, getRemoteNodeClosestNodes, syncNodeGraph etc?

@CMCDragonkai

[CMCDragonkai]

Some of those methods could an async generator right?

[tegefaulkes]

Yeah, withConnG is an async gen, the others are normal.

[tegefaulkes]

I'm going to update this to use timers instead of a timeout value. this way we can compose timeouts.

[tegefaulkes]

Fixed up the timeouts to use timers.

[emmacasolin]

The resolution of this issue should allow for #353 to be easily completed since it will allow for a timeout to be set for the NodeConnectionManager methods called within the Discovery domain.