[nasa/nos3#550] code formatter

[dacarter22]

Added linter.yml file into the .github/workflows/linter.yml directory for every component submodule and merged all into dev

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.82%. Comparing base (1b52bab) to head (26ce97c).
Report is 57 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev     #568      +/-   ##
==========================================
+ Coverage   72.77%   72.82%   +0.05%     
==========================================
  Files         744      745       +1     
  Lines       91191    91497     +306     
  Branches     6923     6942      +19     
==========================================
+ Hits        66362    66636     +274     
- Misses      24829    24861      +32     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[rjbrown2]

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

• Does your submission pass tests?
  • Freshly provisioned VM via Vagrant
    • Default pathing
  • Direct clone into environment.
• No changes to ./cfg/nos3-mission.xml
• Confirm the following:
  • Flight Software loaded and running successfully
  • Spacecraft in 42 GUI points at sun and telemetry reports SVB (sun vector in body frame) X gets to a value of 1, others 0
• Submodules Updated:
  • Submodule paths correct
  • Submodules merged appropriately into submodule dev branches, or Pull requests created and completed PRIOR to this request.

    Submodules have been modified to perform auto clang formatting.

Changes to Core Features:

• Explanation added as to what your changes do and why they should be included

  Added Linter workflow, and clang rules from cFS to each sub module for auto formatting.

How to test these changes?

• Explanation provided below detailing steps to test and validate changes

  There is no major testing needed to validate these changes. Other than verifying that the auto-format has been performed within the sub modules. (It Has)

Closing Tags

• Add any closing tags, or manually set this PR to close any related issue(s) that this PR resolves.
  closes Code Formatter #550

[rjbrown2]

The auto-commit of a linter will cause the "Checks Passed" portion of the PR to fall off if there are linter changes that are automatically changed.

We've decided that this trade-off is worth it for the automated linting.

Users can still click the workflow circles next to their commits to view these checks, rather than them showing up automatically.

[jlucas9]

Not a big deal for this work, but reminder that merge into dev for each submodule should happen after a PR like this is resolved.

[jlucas9]

As submodules were already merged into dev those pieces were integrated already while closing prior merge requests.

[zlynch2]

Approving, tested nos things look ok

[jlucas9]

Manually confirmed sun pointing and sample CPT passed.