chore: update golangci linter configuration

[chmouel]

Updated gomodguard to gomodguard_v2 for the latest linter version. Also disabled the inline check in govet to reduce false positives during code analysis.

Error was:

level=warning msg="The linter 'gomodguard' is deprecated (since v2.12.0) due to: new major version. Replaced by gomodguard_v2." level=warning
msg="Suggested new configuration:\nlinters:\n  enable:\n    -
gomodguard_v2\n" pkg/acl/owners_test.go:200:37: inline: cannot inline:
type parameter inference is not yet supported (govet) assert.Assert(t,
slices.Contains(tt.want, v), "got = %v, want %v", got, tt.want)
pkg/kubeinteraction/cleanups_test.go:33:34: inline: cannot inline: type
parameter inference is not yet supported (govet) cleanupAnnotations :=
maps.Clone(cleanupLabels) ^ test/pkg/configmap/configmap.go:21:11:
inline: cannot inline: type parameter inference is not yet supported
(govet) maps.Copy(newData, origCfgmap.Data) ^
test/pkg/configmap/configmap.go:22:11: inline: cannot inline: type
parameter inference is not yet supported (govet) maps.Copy(newData,
data)

📝 Description of the Change

🔗 Linked GitHub Issue

Fixes #

🧪 Testing Strategy

• Unit tests
• Integration tests
• End-to-end tests
• Manual testing
• Not Applicable

🤖 AI Assistance

AI assistance can be used for various tasks, such as code generation,
documentation, or testing.

Please indicate whether you have used AI assistance
for this PR and provide details if applicable.

• I have not used any AI assistance for this PR.
• I have used AI assistance for this PR.

Important

Slop will be simply rejected, if you are using AI assistance you need to make sure you
understand the code generated and that it meets the project's standards. you
need at least know how to run the code and deploy it (if needed). See
startpaac to make it easy
to deploy and test your code changes.

If the majority of the code in this PR was generated by an AI, please add a Co-authored-by trailer to your commit message.
For example:

Co-authored-by: Claude noreply@anthropic.com

✅ Submitter Checklist

• 📝 My commit messages are clear, informative, and follow the project's How to write a git commit message guide. The Gitlint linter ensures in CI it's properly validated
• ✨ I have ensured my commit message prefix (e.g., fix:, feat:) matches the "Type of Change" I selected above.
• ♽ I have run make test and make lint locally to check for and fix any
  issues. For an efficient workflow, I have considered installing
  pre-commit and running pre-commit install to
  automate these checks.
• 📖 I have added or updated documentation for any user-facing changes.
• 🧪 I have added sufficient unit tests for my code changes.
• 🎁 I have added end-to-end tests where feasible. See README for more details.
• 🔎 I have addressed any CI test flakiness or provided a clear reason to bypass it.
• If adding a provider feature, I have filled in the following and updated the provider documentation:
  • GitHub App
  • GitHub Webhook
  • Gitea/Forgejo
  • GitLab
  • Bitbucket Cloud
  • Bitbucket Data Center

[chmouel]

/retest

[gemini-code-assist]

Code Review

This pull request updates the .golangci.yml configuration by replacing the gomodguard linter with gomodguard_v2 and disabling the inline check within the govet settings. I have no feedback to provide.

[mathur07]

/lgtm