fix(ObjectStore): Make S3 "connect_timeout" option configurable
Follow up to #46317
The hardcoded connection timeout of 5 seconds may not be enough in some cases, so now it is got from the ObjectStore arguments in Nextcloud configuration, falling back to 5 if not set.
The connection timeout is set in seconds, but decimal precision can be used for subsecond accuracy (for example, 4.2 for 4200 milliseconds).
Note that the option is actually http->connect_timeout when passed to the SDK, but it was kept as a flat connect_timeout rather than a nested http->connect_timeout in the ObjectStore arguments for simplicity.
Documentation: https://github.com/nextcloud/documentation/pull/13226
/backport to stable31
/backport to stable30
Failing tests are unrelated and it seems that they were introduced in #53457
Rebased on latest master to (hopefully) get green CI.