Pods that don't produce any output for a while result in intermittent "unexpected EOF" errors in Tilt console

Expected Behavior

• Tilt silently re-establishes log connection without emitting an error

Current Behavior

• If a Pod doesn't log for a while, presumably due to no I/O and the connection being idle, it gets closed and the following error emitted:

   Error streaming web-7f9b8b65f4-wt97k logs: unexpected EOF
  

Steps to Reproduce

1. tilt up with a Pod that runs indefinitely but is mostly silent/quiet (e.g. echo "hello world"; sleep infinity;")
2. Wait a while 😴

Context

We re-establish connection fine, I think it's just the connection being closed due to being idle.
This is case we handle in various ways (hence it re-establishing connection fine), we might just need to treat this error as expected and not log it (or only do it at Debug level?)

No file, test, or entry point is named. Reproduce the issue with a mostly silent Kubernetes Pod and trace the log-streaming path when the idle connection returns an unexpected EOF. Done means the connection is re-established without an error-level console message, with relevant tests passing.