Restructure CI/CD Pipelines and add pre-commit hooks

[kluge7]

This pull request restructures the CI/CD pipelines to focus solely on checking for linting issues, without automatically committing any changes. The key motivation behind this decision is to follow best practices in CI/CD, where:

• Avoiding Automatic Commits: It’s considered bad practice for pipelines to commit changes because developers may not be aware of what these changes are, leading to confusion or unintended consequences. Additionally, automatic commits from pipelines can clutter the commit history, making it harder to track meaningful changes.

Changes Implemented

1. CI/CD Pipelines:

• Pipelines now perform linting and formatting checks only. If any issues are found, the pipeline will fail, but no changes will be automatically committed.
• This ensures that the responsibility for fixing issues remains with the developer, keeping them in full control of the code changes and maintaining a cleaner commit history.

2. Pre-Commit Hooks:

• Introduced pre-commit hooks that enforce code quality checks before the code is committed. These hooks help catch issues early, ensuring consistency in code style and preventing common issues from reaching the CI/CD stage.
• The pre-commit hooks include formatters (such as black and clang-format) and linters to maintain code style and detect potential issues before commits are made.

3. Formatter-Related Changes:

• A significant portion of the changes in this PR result from the newly implemented formatters. These tools (e.g., black for Python and clang-format for C/C++) automatically reformat code to adhere to consistent coding standards.
• While this PR includes many changes, they are primarily stylistic updates (whitespace, line breaks, etc.) and do not affect the functionality of the code.

[Andeshog]

lgtm