Code auto format config file

[RomanAlexandroff]

Summary

• Add a repository-root .clang-format derived from Arduino IDE 2’s default ClangFormat configuration and tuned toward The Norm Version 3 formatting where ClangFormat supports it.
• Keep ft_ / FT_ prefix rules explicitly out of scope for this project.
• Refactor project tooling so the root Makefile stays a user-facing entrypoint, while Firmware Release Manager internals now live under tools/firmware_release_manager/.
• Extract the Firmware Release Manager’s embedded Python into documented scripts for preflight checks, release metadata handling and OTA manifest updates for better maintainability.
• Ignore generated Python bytecode so local verification artifacts are not committed.

Norm / ClangFormat Gaps

ClangFormat cannot enforce every Norm rule. These still require manual review or a dedicated linter:

• Naming rules such as s_, t_, u_, e_, g_, snake_case, and English identifiers.
• return (value); parentheses.
• Tab between return type and function name.
• Function size, variable count, parameter count, and file-level function count limits.
• Declaration placement rules and ban on declaration-with-initialization.
• Forbidden constructs such as for, do while, switch, case, goto, ternary operators, and VLAs.
• 42 header content/updating and comment placement rules.
• Header guard naming patterns.

Test Plan

• python3 -m py_compile tools/firmware_release_manager/*.py
• make help
• make -C tools/firmware_release_manager help
• make -n release
• make -n publish-manifest
• make -n format all

[RomanAlexandroff]

No blocking issues found.

The branch cleanly adds the root .clang-format and separates Firmware Release Manager internals from the root Makefile, making the root file a much smaller command dispatcher. The Python extraction keeps the original release and manifest behavior while making the logic easier to read and maintain.

Verified with Python compilation and Makefile dry-runs; no actual firmware release or manifest publish was executed.