Refactor repository with pre-commit hooks

[lucasssvaz]

Description of Change

Refactor all code base with the new pre-commit hooks.

Tests scenarios

Tested locally and with CI.

[github-actions]

	Warnings
⚠️	Some issues found for the commit messages in this PR: the commit message "Add Cache and remove pre-commit action": summary looks empty type/action looks empty the commit message "Add Config": summary looks empty type/action looks empty the commit message "Black formatting": summary looks empty type/action looks empty the commit message "Clang-format fixes": summary looks empty type/action looks empty the commit message "Fix flake and make Vale manual": summary looks empty type/action looks empty the commit message "Fix flake and reformat": summary looks empty type/action looks empty the commit message "Fix whitespace": summary looks empty type/action looks empty the commit message "Fix": summary looks empty type/action looks empty the commit message "Improve bot message": summary looks empty type/action looks empty the commit message "Improve cache tag": summary looks empty type/action looks empty the commit message "Improve caching": summary looks empty type/action looks empty the commit message "Line endings": summary looks empty type/action looks empty the commit message "Manual fixes": summary looks empty type/action looks empty the commit message "Prettier fixes": summary looks empty type/action looks empty the commit message "Remove freeze": summary looks empty type/action looks empty the commit message "Update action": summary looks empty type/action looks empty the commit message "Use latest stable Python 3 version": summary looks empty type/action looks empty the commit message "[pre-commit.ci lite] apply automatic fixes": summary looks empty type/action looks empty the commit message "fix(typos): Fix more typos": summary looks too short the commit message "fix(typos): Fix typos": summary looks too short Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).
⚠️	Please consider squashing your 40 commits (simplifying branch history).

	Messages
📖	This PR seems to be quite large (total lines of code: 121212), you might consider splitting it into smaller PRs

👋 Hello lucasssvaz, we appreciate your contribution to this project!

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- Addressing info messages (📖) is strongly recommended; they're less critical but valuable.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against f7796d4

[lucasssvaz]

CI hardware tests failing are unrelated to this PR. Looks like there some issue on the runners.