Report _all_ lint failures at once

Otherwise, a CI run reports 3 issues, we fix them, and the
CI run reports _next_ 3 issues. That's a waste of time all around,
and it does not allow judging the scale of the issue.

Signed-off-by: Miloslav Trmač <[email protected]>

Author: mtrmac

common/.golangci.yml

@@ -87,3 +87,7 @@ linters:
           - contextcheck
         path: libimage
         text: LookupImage
+
+issues:
+  max-issues-per-linter: 0
+  max-same-issues: 0

image/.golangci.yml

@@ -16,3 +16,7 @@ linters:
       - comments
       - common-false-positives
       - std-error-handling
+
+issues:
+  max-issues-per-linter: 0
+  max-same-issues: 0

storage/.golangci.yml

@@ -18,3 +18,7 @@ linters:
         - all
         - -ST1003 # https://staticcheck.dev/docs/checks/#ST1003 Poorly chosen identifier.
         - -QF1008 # https://staticcheck.dev/docs/checks/#QF1008 Omit embedded fields from selector expression.
+
+issues:
+  max-issues-per-linter: 0
+  max-same-issues: 0