fix(logging): use ConcurrentRotatingFileHandler to fix Windows rollover PermissionError (#44873)

[tuancookiez-hub]

Fixes #44873.

Summary

RotatingFileHandler.doRollover() raises PermissionError [WinError 32]
on Windows when background threads (gateway, agent loop, TTS, subagent
RPC) hold concurrent handles to agent.log, producing noisy tracebacks
on every log emit and pinning the file at the 5 MiB threshold.

The fix swaps stdlib RotatingFileHandler for
concurrent_log_handler.ConcurrentRotatingFileHandler, which uses
copy-then-truncate on Windows (works while the source is open) and
keeps the atomic rename on POSIX. Same constructor signature, drop-in
replacement, no API change.

As defense in depth, the existing doRollover override now wraps
super().doRollover() in try/except PermissionError so any future
transient failure is swallowed silently instead of spamming stderr.

Changes (4 files, ~134 lines)

• hermes_logging.py — parent class swap, try/except wrap, idempotency check, docstring
• pyproject.toml — exact-pinned concurrent-log-handler==0.9.29 with justification comment
• uv.lock — lock entry for the new dep + portalocker
• tests/test_hermes_logging.py — isinstance checks updated to use the new _ROTATING_BASE selector

Verification

Multi-thread Windows repro at maxBytes=256:

• 8 threads × 80 emits (640 records)
• 3 backup files created
• 0 errors
• 0 stderr tracebacks

Test suite: 60/62 pass. The 2 test_managed_mode_* failures are
pre-existing on Windows (Python's os.chmod is a no-op for Unix
permission bits) and out of scope per the project's one-fix-per-PR
convention.

Tradeoffs

• One new direct dep. Apache-2.0, 110M+ lifetime downloads, used by
  Django and AWS CLI for the same reason. Could be gated as an
  extras_require (win-only) but every Windows install hits this once
  agent.log reaches 5 MiB, so base install seems right.
• CLH creates .__filename.lock files next to each log (multi-process
  safety). Harmless; same pattern stdlib's SMTPHandler uses.