fix(lint): replace loopvar linter

[kobakaku]

Description

Replace loopvar linter in the .golangci.yml.

closes: #7441

TODO

Need to fix lint errors in another PR.

Test

$ make lint
--> Running linter
linting module github.com/cosmos/ibc-go/v9 [2024-10-13T04:43:49]
modules/apps/27-interchain-accounts/controller/keeper/keeper_test.go:143:3: The copy of the 'for' variable "tc" can be deleted (Go 1.22+) (copyloopvar)
                tc := tc
                ^
modules/apps/27-interchain-accounts/controller/keeper/keeper_test.go:320:3: The copy of the 'for' variable "tc" can be deleted (Go 1.22+) (copyloopvar)
                tc := tc
                ^
modules/apps/27-interchain-accounts/controller/keeper/migrations_test.go:45:3: The copy of the 'for' variable "tc" can be deleted (Go 1.22+) (copyloopvar)
                tc := tc
                ^
modules/apps/27-interchain-accounts/controller/keeper/msg_server_test.go:70:4: The copy of the 'for' variable "tc" can be deleted (Go 1.22+) (copyloopvar)
                        tc := tc
                        ^
modules/apps/27-interchain-accounts/controller/keeper/msg_server_test.go:150:4: The copy of the 'for' variable "tc" can be deleted (Go 1.22+) (copyloopvar)
                        tc := tc
                        ^
modules/apps/27-interchain-accounts/controller/keeper/msg_server_test.go:244:3: The copy of the 'for' variable "tc" can be deleted (Go 1.22+) (copyloopvar)
                tc := tc

.... (many lint errors below)

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against the correct branch (see CONTRIBUTING.md).
• Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
• Code follows the module structure standards and Go style guide.
• Wrote unit and integration tests.
• Updated relevant documentation (docs/).
• Added relevant godoc comments.
• Provide a conventional commit message to follow the repository standards.
• Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
• Re-reviewed Files changed in the GitHub PR explorer.
• Review SonarCloud Report in the comment section below once CI passes.

[colin-axner]

Thank you @kobakaku!

[DimitrisJim]

Need to fix lint errors in another PR.

Is this supposed to result in some linting errors? How come they don't show up? Either way, this lgtm but if linting errors do pop up, might make sense to fix here?