Make HttpURLConnection connection inactivity timeout configurable and add test for harvester code

[surbhiia]

Made connection inactivity timeout ms configurable and added a test case for harvester code.

Next items for future PRs:

• Discuss the requirement for custom spanName/status function configuration - is it needed per instrumentation or at the sdk level works.
• Migrate HttpURL instrumentation to utilize AndroidInstrumentation API for install and configuration.

[marandaneto]

should we check if the value here is at least positive and non zero?

[surbhiia]

It does make sense for it to be positive for production workflows. I can throw an IllegalArgumentException if it's negative or zero. Does that make sense?

We will need another test method then, similar to this where we allow for negative values:
public static void setConnectionInactivityTimeoutMsForTesting(long timeoutMs) {
HttpUrlInstrumentationConfig.connectionInactivityTimeoutMs = timeoutMs;
}

If the customer wants to test the harvester with this they can as well use it, so no issue in exposing this to the customer?

[breedx-splk]

Conventionally, zero has been used for a long time to mean "no timeout, wait forever". Not sure how much we need or care about that here. Just throwing an exception for negative seems reasonable to me.

[surbhiia]

Added an exception for negative values! Also added a test only function to allow negative values for test, so wait times are not needed in test.

Added some good documentation to prevent misuse. We can also add @VisibleForTesting annotation on the test function. Right now held off on that as I think we're not using the annotation beyond documentation purposes and we need to introduce additional dependency in this module for just one function. Let me know if it's better to have that annotation instead OR a 1ms wait time in the test functionality instead of this additional function.

[breedx-splk]

Just a small nit, but looks good to me otherwise.