Add Detox tests for each top-level "module" and tab

[hawkrives]

• add detox tests for each module/tab
• test out running multiple simulators on the same macos box (seeing if running 3 simulators is faster than 1, since the macOS boxes are tri-core)

Part of #6788

[hawkrives]

Before I can bring this out of Draft, I need:

• detox to work on CI
• to implement shorter timeouts for our tests - no single test takes over 10s, so I propose that instead of the current 120s
• to figure out if one, two, or three parallel runners work best
• to figure out if we should shard the runners across machines too

[drewvolz]

As far as I can tell, CI should be passing if we weren't using live data for the menus (Carleton menus show "Closed for spring break")