HttpClient: Fix for not timing out queued requests

We would not watch the future until we started processing the request.  This means that if we never started processing the request it would never timeout.
This could have been so bad that eventually we might request a watchdog with a negative timeout.
As an added bonus this reduces the variation of timeouts we may request from the WatchdogCache, allowing it to be much more efficent.

Author: jentfoo

client/src/main/java/org/threadly/litesockets/client/http/HTTPClient.java

@@ -333,8 +333,6 @@ private void processQueue() {
   private void process(HTTPRequestWrapper hrw) {
     if(hrw != null) {
       try {
-        sei.watchFuture(hrw.slf, hrw.timeTillExpired()+1);
-        
         hrw.updateReadTime();
         hrw.client = getTCPClient(hrw.chr.getHTTPAddress());
         inProcess.put(hrw.client, hrw);
@@ -520,12 +518,14 @@ private class HTTPRequestWrapper implements HTTPResponseCallback {
     private TCPClient client;
     private long lastRead = Clock.lastKnownForwardProgressingMillis();
 
-    public HTTPRequestWrapper(ClientHTTPRequest chr) {
+    private HTTPRequestWrapper(ClientHTTPRequest chr) {
       hrp = new HTTPResponseProcessor(chr.getHTTPRequest()
                                          .getHTTPRequestHeader()
                                          .getRequestMethod().equals("HEAD"));
       hrp.addHTTPResponseCallback(this);
       this.chr = chr;
+      
+      sei.watchFuture(slf, chr.getTimeoutMS());
     }
 
     public void updateReadTime() {

gradle.properties

@@ -1,5 +1,5 @@
 group = org.threadly
-version = 0.17
+version = 0.18
 threadlyVersion = 5.18
 litesocketsVersion = 4.3
 org.gradle.parallel=true