Use RobotCapabilities

[itsarune]

Description of the task

We have the ability to define RobotCapabilities for various robots. If these are set for a robot, then the tactic assignment algorithm will take into account the robot's capabilities during assignment. We don't currently use this feature.

The task: add the ability in Thunderscope to add/remove capabilities from robots through a widget.

Possible approach:

1. Add a new widget to add/remove RobotCapability to robots that are currently on the field. A possible design is a drop-down that allows us to select a robot and checkboxes to select which capabilities it has.
2. Create a new proto that maps the robot id to theRobotCapability` it has. It would look something like this.
3. Once a change to capabilities is made, we should send this new proto to full system
4. Add listeners for this proto in backend.cpp and unix_simulator_backend.cpp
5. Add an appropriate callback for the proto you made in SensorFusion
6. SensorFusion should keep track of a map of the robot id to the unavailable RobotCapabilities of that robot
7. Pass the unavailable capabilities to the Robot constructor and update SensorFusion::createFriendlyTeam to accept the current unavailable capabilities for each robot

Acceptance criteria

• In Thunderscope, we should be able to see that setting that a robot cannot kick/chip/move/dribble and observe that it affects tactic assignment
• Create new unit tests in [sensor_fusion_test.cpp](https://github.com/UBC-Thunderbots/Software/blob/master/src/software/sensor_fusion/sensor_fusion_test.cpp) to test the new logic you added

Blocked By