Check common Thunderscope launch arguments in CI

[itsarune]

Description of the task

Thunderscope--due to its Pythonic nature--is very prone to runtime bugs due to incorrectly configured widgets, types, etc. We should have CI in PRs sanity check the most common runtime arguments to Thunderscope so that we don't have to manually checkout each branch and check for breaking changes.

Here is an example of how CI could run Thunderscope on a headless machine

Here are common runtime arguments we should check:

1. bazel run //software/thunderscope:thunderscope_main -- --run_blue --run_diagnostics --interface lo --keyboard_estop
2. bazel run //software/thunderscope:thunderscope_main -- --blue_log {path_to_replay_log} [usually /tmp/tbots/blue/protolog_{timestamp}/]
3. bazel run //software/ai/hl/stp/tactic:goalie_tactic_test -- --enable_thunderscope

Acceptance criteria

• If any of the Thunderscope commands has an error (some kind of a runtime error or type mismatch error), then the CI action should fail

Blocked By