Fix linters in CI

[yurnov]

SUMMARY

It seems that recent updates in linters break CI. Closes #874

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

CI

ADDITIONAL INFORMATION

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/1546fdf527c240eb9d6fdc5c1afb4249

✔️ ansible-galaxy-importer SUCCESS in 4m 55s
✔️ build-ansible-collection SUCCESS in 5m 18s

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/13158ce56489404b84e406ab90197c82

✔️ ansible-galaxy-importer SUCCESS in 4m 18s
✔️ build-ansible-collection SUCCESS in 5m 39s

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/e85070d2ac864db8adbebf448d009787

✔️ ansible-galaxy-importer SUCCESS in 2m 51s
✔️ build-ansible-collection SUCCESS in 5m 21s

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/b95fe695ba4048278447bd5899e021ee

✔️ ansible-galaxy-importer SUCCESS in 5m 26s
✔️ build-ansible-collection SUCCESS in 5m 19s

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/d994ecb45fe44f35a854c89d66457ebd

✔️ ansible-galaxy-importer SUCCESS in 3m 48s
✔️ build-ansible-collection SUCCESS in 5m 14s

[softwarefactory-project-zuul]

Build succeeded (gate pipeline).
https://ansible.softwarefactory-project.io/zuul/buildset/e25d27f6e394459f8aac51796e634d9a

✔️ ansible-galaxy-importer SUCCESS in 8m 57s
✔️ build-ansible-collection SUCCESS in 5m 18s

[patchback]

Backport to stable-3: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 91df2f1 on top of patchback/backports/stable-3/91df2f10bc254633a8892118da0ce589703ec514/pr-873

Backporting merged PR #873 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible-collections/kubernetes.core.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-3/91df2f10bc254633a8892118da0ce589703ec514/pr-873 upstream/stable-3

4. Now, cherry-pick PR Fix linters in CI #873 contents into that branch:

   $ git cherry-pick -x 91df2f10bc254633a8892118da0ce589703ec514

   If it'll yell at you with something like fatal: Commit 91df2f10bc254633a8892118da0ce589703ec514 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 91df2f10bc254633a8892118da0ce589703ec514

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix linters in CI #873 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-3/91df2f10bc254633a8892118da0ce589703ec514/pr-873

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to stable-5: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-5/91df2f10bc254633a8892118da0ce589703ec514/pr-873

Backported as #876

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.