add on enable and on disable to test

[LucienMorey]

Went in to deal with on_enable not being called in test and found out that on_disable gets double called for teleop and auto mode.

[LucienMorey]

Is it worth adding a unit test while I am here to check that these methods run in the modes indicated in the docs? It looks like I might be able to do something similar to the test_feedbacks_with_type_hints test in test_magicbot_feedback.py and call each mode manually? i figure I just need a counter for each thing and then I can assert the expected increases as I go through each mode

[virtuald]

This seems good to me. A test would be nice, but if it's hard I won't require it.

I guess I'm surprised you decided to not call the execute() functions from test mode? But maybe that's just too much.

[auscompgeek]

I'm surprised you decided to not call the execute() functions from test mode?

IMO test mode should be a "get out of your way and avoid doing too much magic" mode. If you think calling on_enable() in test mode makes sense, then that's fine by me too. Wasn't sure if there was any particular rhyme and reason initially for not doing so.

[auscompgeek]

It's always struck me as odd that on_disable() is double-called when disabling the robot. We can follow up with some tests in another PR.