Add improved timeout handling for HTTP transactions.

Introduces AIHTTPTimeoutPolicy objects which do not just
specify a single "timeout" in seconds, but a plethora of
timings related to the life cycle of the average HTTP
transaction.

This knowledge is that moved to the Responder being
used instead of floating constants hardcoded in the
callers of http requests. This assumes that the same
timeout policy is wanted for each transaction that
uses the same Responder, which can be enforced is needed.

I added a AIHTTPTimeoutPolicy for EVERY responder,
only to make it easier later to tune timeout values
and/or to get feedback about which responder runs
into HTTP errors in debug output (especially time outs),
so that they can be tuned later. If we already understood
exactly what we were doing then most responders could
have been left alone and just return the default timeout
policy: by far most timeout policies are just a copy
of the default policy, currently.

This commit is not finished... It's a work in progress
(viewer runs fine with it though).

indra/newview/llfloaterreporter.cpp

@@ -96,6 +96,9 @@
 
 const U32 INCLUDE_SCREENSHOT  = 0x01 << 0;
 
+class AIHTTPTimeoutPolicy;
+extern AIHTTPTimeoutPolicy userReportResponder_timeout;
+
 //-----------------------------------------------------------------------------
 // Globals
 //-----------------------------------------------------------------------------
@@ -858,7 +861,7 @@ public:
 class LLUserReportResponder : public LLHTTPClient::Responder
 {
 public:
-	LLUserReportResponder(): LLHTTPClient::Responder()  {}
+	LLUserReportResponder() { }
 
 	void error(U32 status, const std::string& reason)
 	{
@@ -870,6 +873,7 @@ public:
 		// we don't care about what the server returns
 		LLUploadDialog::modalUploadFinished();
 	}
+	virtual AIHTTPTimeoutPolicy const& getHTTPTimeoutPolicy(void) const { return userReportResponder_timeout; }
 };
 
 void LLFloaterReporter::sendReportViaCaps(std::string url, std::string sshot_url, const LLSD& report)