Forward `enabled_motors` set from motor.cpp to thunderscope

[GrayHoang]

Assuming #3425 is merged, motor.cpp will have a field called enabled_motors that represents the motors that are currently usable (out of the 4 drive motors and the dribbler).

The motor driver code is organized to disable any motors that experience multiple critical faults in a short amount of time.

We should find a way to communicate to thunderscope (and the AI) that a motor has been disabled, so that we can see in real time which motor on which robot has failed.

From what I know, there are a couple of ways to achieve this.

1. We could protobuffer enabled_motors through to the thunderscope level code.
2. @wmostrenko mentioned something about passing motor fault information through to robot diagnostics. I believe it's a flag in sensor_fusion.cpp? Depending on the information sent, this might be enough to help the AI determine which motor has been disabled and plan accordingly.

Acceptance criteria

• [ ] Thunderscope logs which motor has faulted (and the fault) on a robot, and when that fault occured.

Blocked By