CAN frame not stable errors

Every couple (some estimates below) deploys, the robot had massive CAN issues that resulted in unwanted behavior. To be honest, I don't remember was behaviour it caused but I remember it being bad.

We found that just redeploying, restarting the robot code (more likely the core trigger was robot code booting up) or rebooting the RoboRio temporarily fixed the issue until a few deploys more and it came back. Since it was easily dismissable we focused our time elsewhere.

I found that anytime these issues came up, there was also a message that said, "FRC pid XXXX did not die within 500ms. Force killing with kill -9". The core thing about this is the kill -9 on the end. It means that something had to be forcibly shut down. This Chief Delphi post talks a bit about it. One of the people in the post had an open I2C port that was causing it. [Cheif Delphi Post](https://www.chiefdelphi.com/t/ctre-library-not-initialized-correctly-after-frc-pid-xxxx-did-not-die-withing-500ms/376814/9)

I found a Colour Sensor that was being constructed on an I2C port but never used. I did a commit a while ago to stop it from being constructed. I think this could get rid of this issue but no one has done any work on the robots since that change was made so it is **untested**.

I don't know how to reference commits properly, hope this link works https://github.com/FRC2706/2021-2706-Robot-Code/commit/c30c71a952a026118be5516118d979d41d2a9cdf.

Start with commit c30c71a952a026118be5516118d979d41d2a9cdf and inspect the Colour Sensor construction on the I2C port. Reproduce the deploy or robot restart behavior if hardware is available, then verify whether the CAN errors and forced FRC process termination recur after the unused sensor is no longer constructed.

Written by the indexing model from the issue text.