… environment

I have set the `defect_detector` as the default development environment for the duration of this Pull Request.

…eck flag

This exposes the unused functions to Cppcheck and will cause my Defect Detector to fail from now, until I re-factor this later on in the Pull Request.

…o Cppcheck source filters

This ensures Cppcheck iterates through every C++ source file in CRSF for Arduino's code-base

Cppcheck will iterate through all files in the `examples` directory in addition to all files in the `src` directory

These are the coding rules CRSF for Arduino MUST comply with, in order for my Quality Control CI to pass.

This outlines what version of the MISRA rules are being used and what deviations from the standard rules exist within CRSF for Arduino's code-base.

This contains a disabled `unusedFunction` flag, because I currently want to have any unused functions exposed to both Cppcheck and the MISRA compliance add-on.

…ntrol.ini` configuration file.

But leave it disabled, for now.

…rol.ini` configuration file.

But leave it disabled, for now.

…ssions.txt`

Cppcheck will now iterate across CRSF for Arduino's code-base, and flag it for any coding errors.

Global declaration for now. Missing Includes are currently false positives, because Cppcheck does not know where these files are, yet my compiler does.

Global declaration for now. Unmatched Suppressions here are false positives, because for some reason, Cppcheck is not seeing when a particular suppression is actually working.

Global declaration for now. I am intentionally suppressing all unused functions for the time being, because things like `loop()` and `setup()` appear as false positives, along with CRSF for Arduino's own API appearing as false positives.

… Arduino's entire code-base

Cppcheck now checks CRSF for Arduino for compliance with MISRA C 2012 rules in addition to its own checks.

… Matrix

This will be populated with each MISRA C:2012 guideline that CRSF for Arduino is compliant with.

…rc_filter`

This concludes the addition of missing rules.

This explains what each rule flag means

…d add a section for documenting deviations from the MISRA C guidelines

…icons

These emoticons depict where and how this guideline is checked

…ine is checked and where

… for manual review

…eckmarks and crosses

This indicates how each guideline is checked

…tly violated rules

There are currently 774 MISRA C violations in CRSF for Arduino. The Compliance Matrix now shows manual review of these violated rules until each one can be resolved.

… separate tables, and expand on the information provided.

…ed**, and **Mandatory** flags.

This provides a better description of how each flag applies to CRSF for Arduino.

This completes the compliance matrix for CRSF for Arduino