Support for timeout propagation in async requests

[dxxyy]

Feature Request

Currently the methods handling the request/reply pattern exposed in the Connection class don't have support for propagating a timeout for async clients.

Use Case:

We are using the async request/reply pattern in our Java application. While testing at 10TPS, we have noticed high memory usage with reachable objects not being properly garbage collected in a timely manner.

The async clients using the request implementation in NatsConnection don't have the possibility to pass a timeout to the NatsRequestCompletableFuture being created, which is using a default hardcoded timeout of 10 minutes: NatsRequestCompletableFuture.

Proposed Change:

New API exposed, proposition in PR: #617

Who Benefits From The Change(s)?

Any client using the request/reply pattern in asynchronous way.

Alternative Approaches

Leave as is, I don't see an alternative as the current timeout is private and hardcoded in NatsRequestCompletableFuture

[dxxyy]

Resolved via #617