fix: replace silent catch {} with log warnings

[kacy]

Summary

• log warning when api server SO_REUSEADDR or read timeout setsockopt fails
• log warning when tls proxy fails to write redirect, acme challenge, close_notify, or encrypted data responses
• log warning when gpu cgroup device file writes fail
• log warning when deployment status updates fail during batch rollback/pause

11 silent catch {} sites replaced with log.warn(...) across 7 files. These were making production debugging impossible for transient failures.