fix(ci): let ci check go-lint and remove go-lint in Dockerfile

[yexuanyang]

In additional, fix the typo errors in Dockerfile. I remove the unused tool golangci-lint.

[yuluo-yx]

hi The Dockefile has been restored to its previous state. Please check it again. Additionally, I think golint should be placed after go test and build because they have a sequence relationship. For example, after golint is executed, test and build are performed. Placing it as a linter seems inappropriate. WDYT？

[yexuanyang]

Yeah, you are right! Put the golint before go test and go build in workflow 🛠️ Build and Test is better.

[yexuanyang]

I see the go-lint action is commented now, are there some reasons?

hertzbeat-collector-go/.github/workflows/build-and-test.yml

Lines 26 to 35 in d627247

	jobs:
	Build:
	runs-on: ubuntu-22.04
	steps:
	- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
	- uses: ./tools/github-actions/setup-deps
	- run: make fmt
	# todo: 暂时关闭
	# - run: make go-lint
	- run: make build

[yuluo-yx]

I see the go-lint action is commented now, are there some reasons?

hertzbeat-collector-go/.github/workflows/build-and-test.yml

Lines 26 to 35 in d627247

	jobs:
	Build:
	runs-on: ubuntu-22.04
	steps:
	- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
	- uses: ./tools/github-actions/setup-deps
	- run: make fmt
	# todo: 暂时关闭
	# - run: make go-lint
	- run: make build

emm～ maybe because it has many lint error?

[yuluo-yx]

这是可选的，Github 上并不需要此配置。可以恢复下