APIcast fails to boot if one of the OIDC issuers is configured to a URL that does not respond

If one of the OIDC issuer endpoints is configured to a URL that never responds, for any of the configured services, the gateway will fail to boot and hang as visible in the attached logs, thus making all the other (correctly configured) services unavailable.

Attached an example of a Product configuration that results in this behaviour.

It would be useful to add logs for the outbound requests to the OpenID provider both when the request succeeds and fails (including any information about the failure such as timeout etc). This would make debugging much easier especially in the scenarios where there are many unique OIDC endpoints in the configuration and only 1 is causing the problem.