Static analysis, code check, code format

[navidpadid]

This pull request introduces a comprehensive static analysis and code quality system for the kernel module project, along with improved developer experience and documentation. The changes add support for multiple code quality tools (clang-format, sparse, cppcheck, checkpatch), automate their integration in both the dev container and CI/CD pipeline, and provide clear documentation and configuration files. The Makefile and README are updated to reflect these enhancements, ensuring consistent coding style and easy access to quality checks for all contributors.

Static Analysis and Code Quality Integration

• Added new static analysis and formatting configuration files: .clang-format (Linux kernel style), .cppcheck-suppressions (kernel-specific suppressions), and .editorconfig (consistent editor settings). [1] [2] [3]
• Updated Makefile to include targets for static analysis (checkpatch, sparse, cppcheck), code formatting (format, format-check), and a unified check target to run all checks. Help output and phony targets are expanded to document these additions. [1] [2]
• Enhanced CI/CD pipeline (.github/workflows/ci.yml) to run static analysis and formatting checks in a dedicated job, and added a separate unit test job for improved test separation.

Dev Container and Developer Experience

• Updated dev container configuration (.devcontainer/Dockerfile, .devcontainer/devcontainer.json) to pre-install all static analysis tools and automatically set up Git pre-commit hooks for code quality enforcement. [1] [2]
• Improved documentation in README.md to highlight automatic setup of analysis tools and hooks, describe all code quality targets, and provide usage instructions for each tool. [1] [2] [3] [4] [5] [6] [7] [8]

Documentation Updates

• Added a new section in README.md detailing the static analysis workflow, configuration files, and best practices for kernel coding style. [1] [2]
• Updated scripts/README.md to clarify the role of testing scripts and emphasize the use of the dev container for development.