Different default timeouts for connectionIdle on server and client

When using http "Persistent Connections" in rare cases it may happen that the client starts sending on an existing connection very short before the 30.000 ms idle timeout occurs,
but in that moment the servers idle-timeout happens.

Cause is an

java.io.IOException: Remotely closed

Proposed solution 1)
Take different values for DEFAULT_CONNECTION_IDLE_TIMEOUT in

/mule-4/modules/http/src/main/java/org/mule/runtime/module/http/internal/listener/DefaultHttpListenerConfig.java

and

/mule-4/modules/http/src/main/java/org/mule/runtime/module/http/internal/request/DefaultHttpRequesterConfig.java

(e.g. Server (Listener): 60*000)

Solution 2:
Remove "final" on field DEFAULT_CONNECTION_IDLE_TIMEOUT in DefaultHttpListenerConfig

Workaround: specify connectionIdleTimeout="60000" on each http:listener-config