fix: add timeout getMultichainClient to prevent remove connections fr…

[elribonazo]

Improve getMultichainClient by adding the requestTimeout property.

This will apply in 2 areas:

1. ensureInitialized will now have the ability to wait for extra time (allowing remote connections to establish)
2. on each request, createSession, getSession, revokeSession and invokeMethod, it will also wait for extra time before dropping the connection rather than waiting forever

[jiexi]

i don't think we want to wrap this in a retry helper

[elribonazo]

Hmm, we do want it but setting retries to 0, so we would only use timeout

[EdouardBougon]

Would it be possible to delegate timeout handling to the transport instead?

const transport = getMyCustomTransport({ defaultTimeout: 1500}).
const client = getMultichainClientApi({ transport });

In case of a timeout from the transport, we could throw a TransportTimeoutError extending TransportError.
And in withRetry, instead of using a timeout with setTimeout, we just wait for the transport to throw TransportTimeoutError.

And we could also allow overriding the timeout value in the transport.request method.