Start tracking until it goes zero

[kevincobain2000]

I wanted to use this linter TBH. In my company we have started using it too.

Reason for this pull request is because

I looked at the errors produced by the linter. It is a half day job to fix the errors. I don't think we are going to be fixing the lint errors anytime soon. However, we can still add the linter and at least start tracking the counts to go down.

╭─pulkit.kathuria@JP-GCJKVGQK0G^M ~/git/gobrew ‹feature/golangci-lint-fix●›
╰─$ golangci-lint run ./... | grep  -c "\^"                                                                                                                                                                                                           130 ↵
25
╭─pulkit.kathuria@JP-GCJKVGQK0G^M ~/git/gobrew ‹feature/golangci-lint-fix●›
╰─$ echo $?
0

[github-actions]

CoverItUp Report

TYPE	MASTER	FEATURE/GOLANGCI-LINT-FIX
coverage	60.5%	59.2%-
build-time	3sec	25sec+
go-binary-size	6.1kKB	6.1kKB
go-mod-dependencies	29	28-
go-sec-issues	6	6
unit-test-run-time	18sec	19sec+
go-lint-errors	0	25+

Add Badges and Charts to Readme

[kevincobain2000]

ah yes and I removed the separate workflow file.
Once we have zero counts on the lint, will update this CI to exit 1 upon any errors.