Update linter config to new schema

[ReToCode]

Context

golangci-lint now uses depguard V2 which has a totally different (and breaking) configuration syntax. References:

• v1.53.x invisibly breaks configs that were valid in v1.52.x if they used depguard golangci/golangci-lint#3906
• Reusing configuration OpenPeeDeeP/depguard#56
• https://golangci-lint.run/usage/linters/#depguard

Proposed Changes

• Update linter depguard config to new schema

/assign @skonto
/assign @dprotaso

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ReToCode

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ReToCode]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (74019af) 86.04% compared to head (74b94a1) 86.05%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #14691      +/-   ##
==========================================
+ Coverage   86.04%   86.05%   +0.01%     
==========================================
  Files         197      197              
  Lines       14937    14937              
==========================================
+ Hits        12852    12854       +2     
+ Misses       1776     1774       -2     
  Partials      309      309              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[skonto]

/lgtm

[skonto]

Could we also update lint to be latest eg. 1.55.x?

[ReToCode]

Could we also update lint to be latest eg. 1.55.x?

Already done: knative/actions#179

[dprotaso]

/cherry-pick release-1.12

[knative-prow-robot]

@dprotaso: new pull request created: #14847

In response to this:

/cherry-pick release-1.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.