Caching interval tradeoff between UI freshness and API quota

The default 30-second caching interval in Clouddriver may not align with operational needs. More frequent caching (lower intervalSeconds) provides fresher UI data but increases API calls to cloud providers, potentially hitting rate limits or quota. Less frequent caching reduces API load but shows stale infrastructure state.

Adjust redis.poll.intervalSeconds in ~/.hal/$DEPLOYMENT/profiles/clouddriver-local.yml based on requirements. Lower the value (e.g., 15s) for environments needing real-time visibility with sufficient API quota. Increase it (e.g., 60s or higher) for large-scale deployments approaching cloud provider rate limits or where staleness is acceptable.