Bazel remote cache resolves correctly on Scaleway Apple Silicon CAPI runners

Tuist Bazel builds on CAPI-provisioned Scaleway Apple Silicon runners now warm from the remote cache instead of silently falling back cold. tuist bazel setup derives its gRPC target from the cache endpoint URL, but the cache used to expose HTTP and REAPI gRPC on separate listeners; the REAPI GetCapabilities handshake landed on the plain HTTP listener, so .bazelrc.tuist was never written and runner builds fell back to a cold cache. This Scaleway Apple Silicon CAPI provider release ships the co-hosted listener, which serves both the HTTP cache API and h2c REAPI gRPC on a single port (4000 by default, or 4443 with TLS and ALPN negotiation), so the gRPC target derived from the same cache endpoint resolves correctly. The provider’s required network carve-outs shrink to that single port.