Implement Standard Linting for Go Code

[ANU7MADHAV]

I noticed the following issues in the project

Usage of deprecated package functions.
Basic syntax issues that could be avoided with proper tooling.
These issues can make the codebase harder to maintain and may introduce unexpected behaviour

Describe the solution you'd like
I suggest implementing a standard linting tool, such as golangci-lint, to address these problems.

The linter would help:
Automatically identify deprecated functions and syntax issues.
Enforce best practices and improve code quality.
Reduce the manual effort required for code reviews.

Proposed Solution

Add a linter configuration file to the repository.
Integrate linting checks into the CI/CD pipeline to automate quality checks.
Update the contributor documentation to guide running the linter locally.