Exclude revive's new stdlib-shadowing var-naming check

The golangci-lint v2.9.0 upgrade (previous commit) brought in a newer
revive with an additional var-naming sub-check that flags package
names shadowing Go stdlib package names. It flags three long-standing,
intentional package names in this codebase that predate this PR and
are unrelated to the x/net/Go-version bump: `fs`
(internal/third_party/dep/fs), `driver` (pkg/storage/driver), and
`version` (internal/version). Excluding by the same pattern already
used for revive's redefines-builtin-id exclusions above, rather than
renaming stable, widely-referenced packages to satisfy a newly-enabled
check.

Ref: HELM-821

Author: baijum

.golangci.yml

@@ -44,6 +44,14 @@ linters:
       - linters:
           - revive
         text: 'redefines-builtin-id: redefinition of the built-in function new'
+      # New in the golangci-lint v2.9.0 upgrade (needed for Go 1.26 support, see HELM-821):
+      # revive's var-naming check now also flags package names that shadow stdlib package
+      # names (e.g. `fs`, `driver`, `version`). These are long-standing, intentional names
+      # in this codebase (internal/third_party/dep/fs, pkg/storage/driver, internal/version)
+      # unrelated to this change; not worth renaming packages just to satisfy a new check.
+      - linters:
+          - revive
+        text: 'var-naming: avoid package names that conflict with Go standard library package names'
     paths:
       - third_party$
       - builtin$