fix(logging): catch PermissionError in doRollover (#44873)

[kyssta-exe]

Fixes #44873. On Windows, RotatingFileHandler.doRollover() raises PermissionError [WinError 32] when the log file is locked by another process. The exception was uncaught, causing the stdlib logging error handler to print a full traceback to stderr on every subsequent emit. The fix wraps super().doRollover() in a try/except for PermissionError and OSError, closing and reopening the stream on failure so logging continues writing to the current file.

[liuhao1024]

Verification: Clean implementation ✅

Reviewed the PermissionError handling in _ManagedRotatingFileHandler.doRollover():

• Correct exception hierarchy: catches both PermissionError (Windows WinError 32) and OSError (generic file-lock scenarios).
• Stream recovery: closes the old stream, sets to None, reopens via _open(), and refreshes the stat snapshot — the handler continues writing to the same file instead of crashing.
• Silent failure is correct here: the inner try/except Exception: pass on stream reopen is appropriate — if reopening also fails, the handler degrades gracefully (next emit will try again).
• Test coverage: two tests covering PermissionError and OSError paths, both verifying the handler continues to write after recovery.

Clean fix, no findings.

[alt-glitch]

Duplicate of #44974 — same catch-and-skip mechanism for #44873 (wrap RotatingFileHandler.doRollover() to swallow Windows PermissionError/WinError 32). #44974 is the earliest open PR using this approach. Competing alternative #44921 uses ConcurrentRotatingFileHandler (different mechanism — related).

[kyssta-exe]

Duplicate of #44974 — same PermissionError catch in RotatingFileHandler.doRollover (#44873). Closing as superseded.