fix: MetaDrive simulator on macOS (spawn context, lazy imports)

[AmitabhainArunachala]

Summary

Fixes the MetaDrive simulator so it runs correctly on macOS, allowing tools/sim/tests/test_metadrive_bridge.py to pass.

Closes #33207

Root causes

On macOS, Python's multiprocessing defaults to the fork start method. Panda3D and MetaDrive initialize Cocoa and OpenGL on import, which is unsafe in a forked child process after the parent has set up GUI state.

Additionally:

• dist_threshold = 1 is too aggressive on macOS where simulator ticks produce smaller position deltas, causing false vehicle_not_moving failures
• Synthetic eof = frame_id * 0.05 * 1e9 fails camera freshness checks on macOS
• forkpty in unblock_stdout() is incompatible with macOS simulation

Changes

tools/sim/bridge/metadrive/metadrive_world.py

• Use multiprocessing.get_context("spawn") on Darwin for clean subprocess state
• Use mp_ctx.{Array, Pipe, Event, Process} so all IPC primitives share the spawn context
• Reduce dist_threshold to 0.05 on macOS to avoid false vehicle_not_moving failures

tools/sim/bridge/metadrive/metadrive_process.py

• Remove top-level imports of panda3d and metadrive — these initialized Cocoa in the parent process
• Lazy-load inside apply_metadrive_patches() and metadrive_process(), which run in the child subprocess
• Move C3_POSITION/C3_HPR constants inside the lazy initialization

tools/sim/lib/camerad.py

• Use time.monotonic() for the eof timestamp instead of frame_id * 0.05 * 1e9

system/manager/manager.py

• Skip unblock_stdout() (which calls forkpty) on Darwin when SIMULATION=1

Testing

python -m pytest -vv -s -n0 tools/sim/tests/test_metadrive_bridge.py

[github-actions]

Process replay diff report

Replays driving segments through this PR and compares the behavior to master.
Please review any changes carefully to ensure they are expected.

✅ 0 changed, 66 passed, 0 errors

[AmitabhainArunachala]

Closing this in favor of #38156 which takes a cleaner approach with fewer changes and passes all CI checks. The spawn-context and lazy-import changes in this PR were addressing symptoms rather than root causes — process.py preimport guard is the correct fix since macOS uses spawn by default since Python 3.8.