chore: cleanup warnings from components during compilation

[finger563]

Description

• Change static constexpr char *<name> = "<string>" to static std::string <name>;
• Memset structures to 0 and manually set fields
• Add missing initializers
• Add [[maybe_unused]]
• Disable some warnings on nearby (external) library

Motivation and Context

Library warnings make it harder for developers to find / understand any compilation problems or warnings that may arise from their code. Fixing warnings from our components enables cleaner builds and streamlines development.

How has this been tested?

Building and running in a complex project with many of these components together.

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
• [x] 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.
• [x] All new and existing tests passed.
• [x] My code follows the code style of this project.

[github-actions[bot]]

:white_check_mark:Static analysis result - no issues found! :white_check_mark: