support retry-after in FetcherBolt

[jnioche]

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Retry-After

if a site is asking for a delay, we should enforce it in the internal queues of the FetcherBolt.

[jnioche]

Could use the snippet below

// has a retry after? 503 (Service Unavailable) or 429 (Too Many Requests) 
                	// but also a permanent redir (301)
                    String retry_after = mergedMD.getFirstValue("Retry-After");
                    if (retry_after != null){
                    	// in seconds?
                    	if (retry_after.matches("[0-9]+")) {
                    		int rety_after_secs = Integer.parseInt(retry_after);
                    	}
                    	else {
                    		// expressed as a date
                    		// or a delay in secs
                    		SimpleDateFormat format = new SimpleDateFormat("EEE, dd MMM yyyy HH:mm:ss zzz");
                    		try {
                    			Date d = format.parse(retry_after);
                    			// pass the date
                    			d.toInstant().toString();
                    		}
                    		catch (ParseException pe) {
                    			LOG.debug("Incorrect date found for retry-after: {} - {}",retry_after, url);
                    		}
                    	}
                    }

[rzo1]

See the discussion in #1944 - conclusion is, we should follow #867 as a design approach here.