Lint Go modules

[ferrarimarco]

Fixes #3596
Fixes #4430

Proposed Changes

1. Implement a new mode for the Go linter to run against a directory. This is useful to lint an entire Go project, instead of linting individual files.
2. Introduce a new variable: VALIDATE_GO_MODULES, defaults to true, to enable the this new mode.
3. Fail if there are Go modules to lint, and the user enabled both individual Go files linting and Go modules linting because this may cause false positives.

Readiness Checklist

Author/Contributor

• I included all the needed documentation for this change.
• I provided the necessary tests.

Reviewing Maintainer

• Label as breaking if this is a large, fundamental change.
• Label as either: automation, bug, documentation, enhancement, infrastructure.

BEGIN_COMMIT_OVERRIDE
feat: lint Go modules (#4984)
END_COMMIT_OVERRIDE

[anantdamle]

The variable option is not useful because of following two reasons.
(1) If the repo is a single project, its redundant
(2) If the repo is multi-language project,
(a) the code contributor can conveniently not enable it for their folder
(b) There can be multiple go-lang modules (/directories)

I propose a recursive search for a go.mod file and run it against all those folders.

[ferrarimarco]

The variable option is not useful because of following two reasons.
(1) If the repo is a single project, its redundant

True. It's still worth having it to maintain backward compatibility with the current behavior.

(2) If the repo is multi-language project, (a) the code contributor can conveniently not enable it for their folder (b) There can be multiple go-lang modules (/directories)

I don't get (a), but (b) is true.

I propose a recursive search for a go.mod file and run it against all those folders.

That's a nice idea. With this, the GO_DIRECTORY variable will not be needed.

[zkoppert]

🎉