Port all simulated c++ tests to python

[nycrat]

Description

This PR ports all existing simulated gameplay c++ tests to python (while keeping original pytests)

• Ported simulated c++ gameplay tests to python
• Added some validations that were originally used in c++ tests

Ported Tests

Found using: rg SimulatedErForceSimPlayTestFixture and manual sorting

TACTIC TESTS TO PORT

• src/software/ai/hl/stp/tactic/pivot_kick/pivot_kick_tactic_test.cpp
• src/software/ai/hl/stp/tactic/crease_defender/crease_defender_tactic_test.cpp
• src/software/ai/hl/stp/tactic/halt/halt_tactic_test.cpp
• src/software/ai/hl/stp/tactic/move/move_tactic_test.cpp
• src/software/ai/hl/stp/tactic/kick/kick_tactic_test.cpp
• src/software/ai/hl/stp/tactic/chip/chip_tactic_test.cpp
• src/software/ai/hl/stp/tactic/dribble/dribble_tactic_test.cpp
• src/software/ai/hl/stp/tactic/dribble/dribble_tactic_push_enemy_test.cpp
• src/software/ai/hl/stp/tactic/receiver/receiver_tactic_test.cpp
• src/software/ai/hl/stp/tactic/attacker/attacker_tactic_passing_test.cpp
• src/software/ai/hl/stp/tactic/attacker/attacker_tactic_shoot_goal_test.cpp
• src/software/ai/hl/stp/tactic/attacker/attacker_tactic_keep_away_test.cpp (Add complex pytest validations to attacker tactic test #3638)
• src/software/ai/hl/stp/tactic/penalty_kick/penalty_kick_tactic_test.cpp

PLAY TESTS TO PORT

• src/software/ai/hl/stp/play/shoot_or_pass/shoot_or_pass_play_test.cpp
• src/software/ai/hl/stp/play/stop_play_test.cpp
• src/software/ai/hl/stp/play/shoot_or_chip_play_test.cpp
• src/software/ai/hl/stp/play/crease_defense/crease_defense_play_test.cpp
• src/software/ai/hl/stp/play/free_kick/free_kick_play_test.cpp
• src/software/ai/hl/stp/play/kickoff_friendly_play_test.cpp
• src/software/ai/hl/stp/play/kickoff_enemy_play_test.cpp
• src/software/ai/hl/stp/play/example/example_play_test.cpp
• src/software/ai/hl/stp/play/penalty_kick_enemy/penalty_kick_enemy_play_test.cpp
• src/software/ai/hl/stp/play/penalty_kick/penalty_kick_play_test.cpp (graysons pr Penalty kick play Python test #3050)

SENSOR FUSION TEST

• src/software/sensor_fusion/filter/ball_occlusion_test.cpp

Resolved Issues

resolves #2558, resolves #2778, resolves #3636

Length Justification and Key Files to Review

Porting tests requires lots of changes.

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

[nycrat]

actually, i'll try to break this pr apart to make it easier to review