Remove verbose info logs from GCS and S3 storage adapters while keeping
critical warnings and error messages. This cleanup makes production logs
more actionable and less noisy.
Changes:
- Remove verbose cache check logging (structure details, field validation)
- Remove verbose GCS/S3 operation logs (download progress, parsing steps)
- Remove verbose pagination diagnostic logs (per-shard, per-file details)
- Keep critical warnings for invalid cache, null cache, recovery actions
- Keep error logs for actual failures
- Move successful operation details to trace level
Benefits:
- Production logs are now clean and actionable
- Critical issues still surface with warnings
- Debug details available via trace level when needed
- v3.37.8 cache validation remains fully functional
This completes the GCS persistence debugging journey (v3.35.0 → v3.38.0)