Feat: Add Linting and Code Quality Checks in CI

[noble-varghese]

Description:

Maintaining code quality and adherence to coding standards is essential for the long-term stability and maintainability of our project. While we have some development checks in place, enhancing our Continuous Integration (CI) pipeline with linting and code quality checks can help ensure that our codebase remains clean and consistent. These checks will analyze our codebase for potential issues, such as coding style violations and common errors, helping us catch and address them early in the development process.

Proposed Tasks:

• Integrate a linting tool (Pylint) into our CI pipeline.
• Configure linting rules to match our coding standards.
• Set up code quality checks (e.g., code complexity analysis) as needed.
• Ensure that the CI pipeline fails on linting errors.
• Document linting and code quality procedures for the development team.

Code quality is an ongoing effort; new code submissions should adhere to coding standards.
We welcome community contributions and input on linting rules.

Note: This issue tracks the addition of linting and code quality checks to our CI pipeline. Further discussions and contributions will happen in follow-up discussions and pull requests.

Your involvement in this issue, whether through code contributions, linting rule suggestions, or feedback, is vital as we work to improve code quality in our project.