feat(detekt): add detekt for static analysis and fix issues

[thelooter]

Summary

This PR adds the detekt static code analysis tool to the Kotlin codebase and fixes all issues found by running detekt.

Changes

• Integrated the detekt static code analysis tool
• Configured detekt with a base ruleset to enforce Kotlin coding best practices
• Fixed all code style, potential bugs, and other issues identified by detekt
• Refactored several methods to lower their cyclomatic complexity and limit the number of return statements to two per method
• Added detekt to the project's CI/CD pipeline to run on every PR

Motivation

Detekt is a popular and powerful static code analysis tool for Kotlin that helps identify and fix common code issues. By integrating detekt, we can:

• Improve code quality and maintainability across the codebase
• Catch potential bugs and vulnerabilities early in the development process
• Enforce consistent code styling and formatting
• Establish a strong foundation of Kotlin best practices

Fixing the detekt issues found in this PR will make the codebase more robust, readable, and aligned with industry standards.

It's important to note that static analysis tools like detekt are not a magic bullet. They should be used in conjunction with common sense, manual code reviews, and other quality assurance practices to ensure the highest level of code quality and maintainability.

Testing

• Verified all detekt checks pass locally
• Ensured the CI/CD pipeline successfully runs detekt on the updated codebase