RFR: 8288717: Add a means to close idle connections in HTTP/2 connection pool [v7]

[Conor Cleary]

On Tue, 15 Nov 2022 12:10:00 GMT, Conor Cleary <ccleary at openjdk.org> wrote:

>> **Issue**
>> When using HTTP/2 with the HttpClient, it can often be necessary to close an idle Http2 Connection before a server sends a GOAWAY frame. For example, a server or cloud based tool could close a TCP connection silently when it is idle for too long resulting in ConnectionResetException being thrown by the HttpClient.
>> 
>> **Proposed Solution**
>> A new system property, `jdk.httpclient.idleConnectionTimeout`, was added and is used to specify in Milliseconds how long an idle connection (idle connections are those which have no currently active streams) for the HttpClient before the connection is closed.
>
> Conor Cleary has updated the pull request incrementally with one additional commit since the last revision:
> 
>   8288717: Changed default keep alive value to original

The default Keep Alive time has been kept at its original 1200 seconds. A seperate issue has been created to reduce this default value here: [JDK-8297030](https://bugs.openjdk.org/browse/JDK-8297030)

Seeking additonal reviewers now to move this PR forward

-------------

PR: https://git.openjdk.org/jdk/pull/10183