fix(cli): Docker cleanup config propagation

[MichaelHuangXiaofei]

Fixes #75291

What changed

• Forward docker_persist_across_processes from file-tool and execute_code Docker creation paths.
• Forward docker_orphan_reaper through the same paths.
• Add regression coverage for both entry points.

Root cause

Both paths built a partial container_config. The missing settings fell back to terminal_tool defaults, so an explicit docker_persist_across_processes: false was silently treated as true, leaving the container running and reusable.

Validation

• venv\\Scripts\\python.exe -m pytest tests/tools/test_docker_config_propagation.py tests/tools/test_docker_orphan_reaper_integration.py -q
• Result: 7 passed

[teknium1]

Thanks for tracing both creation paths. The lifecycle propagation premise is confirmed on current main: tools/code_execution_tool.py:771 and tools/file_tools.py:1046 omit these flags, while tools/terminal_tool.py:1596-1609 defaults omitted values to true.

Problems

• tools/file_tools.py:96 and tools/file_tools.py:1288 contain unrelated accidental line splits that corrupt the existing next_offset comments.

Suggested changes

• Restore those two comments unchanged; the two container_config additions and regression coverage otherwise address the verified missing paths. The other source creation paths already forward both values (agent/prompt_builder.py:1086-1087, tools/terminal_tool.py:2389-2390).

Automated hermes-sweeper review.

[teknium1]

This unrelated newline corrupts the existing next_offset comment. Please restore it unchanged; the same accidental split also appears at new-side line 1288.