Fix OOM issue when setting concurrentHTTP1ConnectionsPerHostSoftLimit to Int.max

[aryan-25]

Motivation:

When a user wishes to make the connection pool create as many concurrent connections as possible, a natural way to achieve this would be to set .max to the concurrentHTTP1ConnectionsPerHostSoftLimit property.

HTTPClient.Configuration().connectionPool = .init(
    idleTimeout: .hours(1),
    concurrentHTTP1ConnectionsPerHostSoftLimit: .max
)

The concurrentHTTP1ConnectionsPerHostSoftLimit property is of type Int. Setting it to Int.max leads to Int.max being passed as an argument to Arrays .reserveCapacity(_:) method, causing an OOM issue.

Addresses Github Issue #751

Modifications:

Capped the argument to self.connections.reserveCapacity(_:) to 1024 in HTTPConnectionPool.HTTP1Connections

Result:

Users can now set the concurrentHTTP1ConnectionsPerHostSoftLimit property to .max without causing an OOM issue.

[fabianfett]

we need to use the async/await API here.

[Lukasa]

Love this, very nice.