### profile: details    upstream deliberately sleeping 30s per request
### demo.upstream.timeout-ms = 750, so the indicator gives up long before the stub replies

$ time curl -s http://localhost:8080/actuator/health/externalApi
{
    "details": {
        "error": "org.springframework.web.client.ResourceAccessException: I/O error on GET request for \"http://localhost:8080/stub/upstream/ping\": Read timed out",
        "url": "http://localhost:8080/stub/upstream/ping",
        "latencyMs": 753,
        "timeoutMs": 750
    },
    "status": "DOWN"
}
wall clock: 0.84 s

  The read timeout is what bounds this, not the endpoint. Remove setReadTimeout from
  ExternalApiHealthIndicator and this call blocks for the full 30 seconds, holding a
  Tomcat worker the whole time.