fix(ci): golangci-lint revive var-naming error in linters

[zakisk]

fixed golangci-lint revive var-naming error in linters. this might be happening due new fix release of golangci-lint hours before golangci/golangci-lint#5904

Changes

Submitter Checklist

• 📝 Ensure your commit message is clear and informative. Refer to the How to write a git commit message guide. Include the commit message in the PR body rather than linking to an external site (e.g., Jira ticket).

• ♽ Run make test lint before submitting a PR to avoid unnecessary CI processing. Consider installing pre-commit and running pre-commit install in the repository root for an efficient workflow.

• ✨ We use linters to maintain clean and consistent code. Run make lint before submitting a PR. Some linters offer a --fix mode, executable with make fix-linters (ensure markdownlint and golangci-lint are installed).

[chmouel]

can we disable globally instead in golangci-lint.yaml if we are not using this linter?

[zakisk]

@chmouel I think this is useful for var naming linting and it is enable explicitly golangci.yaml

[chmouel]

I don't understand what do you mean, yes it is useful so then why is it disabled and not fixed in this file? you are not really explaining it on your commit message either..

[zakisk]

I don't understand what do you mean, yes it is useful so then why is it disabled and not fixed in this file? you are not really explaining it on your commit message either..

I am disabling it in those package because revive needs meaningful name of packages (types => bbdctypes or something like this would work) but I think those package names are fine but keeping it enabled to lint newly added package in future.

[chmouel]

You should explain in Pull Request more clearly the reasons you are doing things, it makes easier to review....

[zakisk]

You should explain in Pull Request more clearly the reasons you are doing things, it makes easier to review....

sure, will keep in mind (sorry)