Integrate Clippy and .editorconfig for Improved Code Quality and Consistency

[ukor]

Description of the problem.

Formatting noise (like changes in indentation or line endings) or code that contains non-idiomatic Rust patterns can be frustrating for reviewers and can lead to potential subtle bugs. This issues can b caught by a linter.

Without centralised tools, we lack consistent code quality and uniform styling across different developers and IDEs.

Description of the solution.

We should integrate two industry-standard tools into our Rust project to enforce code quality and style automatically:

Integrate Clippy:

• Add Clippy (the Rust linter) as a mandatory check.

• Configure our top-level files (lib.rs and main.rs) to include #![deny(clippy::all)] to treat all linter warnings as errors, enforcing high standards.

• Add a Clippy step to our CI/CD pipeline so no pull request can be merged if it fails the lint checks.

Add a .editorconfig file:

• Create a root-level .editorconfig file.

• Define core formatting rules

• This ensures that regardless of the editor or IDE (VS Code, IntelliJ, etc.) a developer uses, the saved file will conform to our project's agreed-upon style.

Additional context

The combined benefits of these tools are substantial:

Tool	Focus Area	Key Benefit
Clippy	Code Quality	Catches subtle bugs and enforces idiomatic, best-practice Rust.
.editorconfig	Code Consistency	Guarantees uniform formatting (indentation, line endings) across all developers.

This small up-front effort dramatically reduces code review overhead, prevents preventable bugs, and ensures the codebase remains clean and maintainable in the long run.