[Feat]: Rename golangcilint.yaml to .golangci.yaml

[AndersBennedsgaard]

Is your feature request related to a problem? Please describe.

When editing files, it is annoying having to configure golangci-lint to look for specific configuration files. By renaming the golangcilint.yaml to .golangci.yaml (or another similarly sounding file name), the configuration is automatically picked up when running it, which makes it nicer for developers who have set golangci-lint up to run in their editors

See https://golangci-lint.run/usage/configuration/.

Describe the solution you'd like

Rename golangcilint.yaml to .golangci.yaml, and move custom golangci-lint flags/configuration from

zot/.github/workflows/golangci-lint.yaml

Line 34 in e5eacaa

args: --config ./golangcilint.yaml --enable-all --build-tags debug,needprivileges,sync,scrub,search,userprefs,metrics,containers_image_openpgp,lint,mgmt,imagetrust ./cmd/... ./pkg/...

and

zot/Makefile

Lines 320 to 326 in e5eacaa

	check: ./golangcilint.yaml $(GOLINTER)
	mkdir -p pkg/extensions/build; touch pkg/extensions/build/.empty
	$(GOLINTER) --config ./golangcilint.yaml run --enable-all --out-format=colored-line-number --build-tags containers_image_openpgp ./...
	$(GOLINTER) --config ./golangcilint.yaml run --enable-all --out-format=colored-line-number --build-tags $(BUILD_LABELS),containers_image_openpgp ./...
	$(GOLINTER) --config ./golangcilint.yaml run --enable-all --out-format=colored-line-number --build-tags debug ./pkg/debug/swagger/ ./pkg/debug/gqlplayground
	$(GOLINTER) --config ./golangcilint.yaml run --enable-all --out-format=colored-line-number --build-tags dev ./pkg/test/inject/
	$(GOLINTER) --config ./golangcilint.yaml run --enable-all --out-format=colored-line-number --build-tags stress ./pkg/cli/server/

to the configuration file. This will make it more streamlined for the developer to work locally, since he can expect the same results from running locally and in CI.

It might make sense to introduce the --fast flag in some way though, to speed up linting, but I am not sure if it would be needed

Describe alternatives you've considered

No response

Additional context

No response