Runtime selection of field vs simulated gameplay tests

[nycrat]

Description

This PR combines simulated and field gameplay test runners under the common TbotsTestRunner interface. This allows all tests to be run as either field tests or simulated tests with just a different flag passed into the bazel test command.

This PR contains many refactoring changes to our existing python testing framework. These changes were important to improving code quality while implementing the changes, and they will make it easier to implement #3369 in the future.

• ./tbots.py test move_tactic_test
• ./tbots.py test move_tactic_field_test
• ./tbots.py test move_tactic_test --run_field_test
• ./tbots.py test move_tactic_field_test --run_field_test

Testing Done

... TODO

Resolved Issues

resolves #2908

Length Justification and Key Files to Review

A lot of just renaming and combining the simulated_tests and field_tests under the gameplay_tests package. None of the logic is changed for validations and existing tests.

Important not just refactoring changes to review:

(in src/software/gameplay_tests)

• fixture.py
• util.py
• tbots_test_runner.py
• field_test_runner.py
• simulated_test_runner.py

Review Checklist

It is the reviewers responsibility to also make sure every item here has been covered

• Function & Class comments: All function definitions (usually in the .h file) should have a javadoc style comment at the start of them. For examples, see the functions defined in thunderbots/software/geom. Similarly, all classes should have an associated Javadoc comment explaining the purpose of the class.
• Remove all commented out code
• Remove extra print statements: for example, those just used for testing
• Resolve all TODO's: All TODO (or similar) statements should either be completed or associated with a github issue