feat: add golangci linters

[ishanarya0]

No description provided.

[ishanarya0]

Added golangci linters.
Should we use the following linters as well?

• containedctx
• forcetypeassert
• gochecknoinits
• gocognit
• gomodguard
• nosprintfhostport
• paralleltest
• gofumpt
• nlreturn
• goerr113
• exhaustruct
• forbidigo

[ishanarya0]

[ISSUE] Golangci Github Action is unable to identify some linter(s) hence these failing checks.

[spy16]

I just ticked the ones i think we can use.

• gofumpt - this one would rewrite go files, so may be we could just put it as part of makefile. That way, we always commit properly formatted files.
• nlreturn - i think it's arguable wether this is a good idea or not. Leaving an empty line before every return isn't a good idea in my opinion. I usually prefer to keep relevant things grouped together as much as possible.
• exhauststruct - i don't think it's a good approach to enforce this strictly. Zero-values are in many cases very useful defaults and even recommended by the community. As such, it might be preferable to allow users to init only specific fields.

[ishanarya0]

I just ticked the ones i think we can use.

• gofumpt - this one would rewrite go files, so may be we could just put it as part of makefile. That way, we always commit properly formatted files.
• nlreturn - i think it's arguable wether this is a good idea or not. Leaving an empty line before every return isn't a good idea in my opinion. I usually prefer to keep relevant things grouped together as much as possible.
• exhauststruct - i don't think it's a good approach to enforce this strictly. Zero-values are in many cases very useful defaults and even recommended by the community. As such, it might be preferable to allow users to init only specific fields.

• gofumpt: yes let's add it to make file
• nlreturn: yes, I was unsure about that practice. REMOVING it.
• exhauststrcut: REMOVING it as well.