chore: disable deprecated linters

[grdryn]

---

Description

How Has This Been Tested?

Before (see warnings):

➜ make lint
test -s /var/home/gryan/src/github.com/opendatahub-io/opendatahub-operator/bin/golangci-lint || { curl -sSfL 'https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh' | bash -s v1.61.0; }
/var/home/gryan/src/github.com/opendatahub-io/opendatahub-operator/bin/golangci-lint run --timeout=5m0s --sort-results
WARN The linter 'exportloopref' is deprecated (since v1.60.2) due to: Since Go1.22 (loopvar) this linter is no longer relevant. Replaced by copyloopvar. 
WARN The linter 'execinquery' is deprecated (since v1.58.0) due to: The repository of the linter has been archived by the owner.  

After (no warnings):

➜ make lint
test -s /var/home/gryan/src/github.com/opendatahub-io/opendatahub-operator/bin/golangci-lint || { curl -sSfL 'https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh' | bash -s v1.61.0; }
/var/home/gryan/src/github.com/opendatahub-io/opendatahub-operator/bin/golangci-lint run --timeout=5m0s --sort-results

Screenshot or short clip

Merge criteria

• You have read the contributors guide.
• Commit messages are meaningful - have a clear and concise summary and detailed explanation of what was changed and why.
• Pull Request contains a description of the solution, a link to the JIRA issue, and to any dependent or related Pull Request.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work

[grdryn]

/hold

One of the main reasons to create this PR is to have something innocuous to see if the test flakes seen in #1465 are reproducible on main. My guess is that they are.

[biswassri]

One of the main reasons to create this PR is to have something innocuous to see if the test flakes seen in #1465 are reproducible on main. My guess is that they are.

@grdryn I'm also seeing similar failures on another PR -1456. There is also a flaky test with infrastructure that shows { openshift cluster install failed with infrastructure setup} Maybe this is a infrastructure related error?

[grdryn]

/retest

kueue:

 === RUN   TestOdhOperator/validate_installation_of_kueue_component/e2e-test-dsc/Validate_Disabling_Kueue_Component
    kueue_test.go:75: 
        	Error Trace:	/go/src/github.com/opendatahub-io/opendatahub-operator/tests/e2e/kueue_test.go:75
        	Error:      	Received unexpected error:
        	            	component Kueue is disabled, should not have deployments in NS opendatahub any more
        	Test:       	TestOdhOperator/validate_installation_of_kueue_component/e2e-test-dsc/Validate_Disabling_Kueue_Component
        	Messages:   	error testing kueue component enabled field

[grdryn]

There is also a flaky test with infrastructure that shows { openshift cluster install failed with infrastructure setup} Maybe this is a infrastructure related error?

Yeah that one looks different than the test flakes, I haven't seen that one.

[grdryn]

/unhold

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (main@95f696a). Learn more about missing BASE report.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1475   +/-   ##
=======================================
  Coverage        ?   19.04%           
=======================================
  Files           ?      159           
  Lines           ?    10399           
  Branches        ?        0           
=======================================
  Hits            ?     1980           
  Misses          ?     8195           
  Partials        ?      224           

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

[lburgazzoli]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lburgazzoli

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 [lburgazzoli]

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