Description

• Update espp and esp-protocols submodules
• Update code with any changes required
• Add clang-format and pre-commit hook for code style
• Add github actions workflows for code analysis, building, and packaging / releasing

Motivation and Context

• Uses latest code (which keeps the example up to date)
• Keeps style consistent
• Keeps code quality higher

How has this been tested?

Screenshots (if appropriate, e.g. schematic, board, console logs, lab pictures):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update
• Hardware (schematic, board, system design) change
• Software change

Checklist:

• My change requires a change to the documentation.
• I have added / updated the documentation related to this change via either README or WIKI

Software

• I have added tests to cover my changes.
• I have updated the .github/workflows/build.yml file to add my new test to the automated cloud build github action.
• All new and existing tests passed.
• My code follows the code style of this project.