chore: test pylint with pylint-pytest plugin

[Omeramsc]

Adds the pylint-pytest pylint plugin to help
differentiate between code-relevant and test-relevant issues when running pylint on test files.

more info available on pypi: https://pypi.org/project/pylint-pytest/

[yftacherzog]

@Omeramsc when running in CI, does it solve the issue you raised yesterday?

[Omeramsc]

@Omeramsc when running in CI, does it solve the issue you raised yesterday?

The plugin is from pylint's side, so I modified the static test accordingly, it is not a problem.
It is not a perfect plugin (it doesn't cover all issues, e.g docstrings), but it is an improvment over what we currently have.

[yftacherzog]

@Omeramsc when running in CI, does it solve the issue you raised yesterday?

The plugin is from pylint's side, so I modified the static test accordingly, it is not a problem. It is not a perfect plugin (it doesn't cover all issues, e.g docstrings), but it is an improvment over what we currently have.

My question is whether you confirmed that the change you did is addressing the issue you raised.

[Omeramsc]

@Omeramsc when running in CI, does it solve the issue you raised yesterday?

The plugin is from pylint's side, so I modified the static test accordingly, it is not a problem. It is not a perfect plugin (it doesn't cover all issues, e.g docstrings), but it is an improvment over what we currently have.

My question is whether you confirmed that the change you did is addressing the issue you raised.

I raised multiple issues; The one in the previous PR was solved by changing the code, so it doesn't need to solve it. This plugin doesn't support the issue raised anyway, but it does many others we may or already faced.
as for the "running in CI issue" (I also mentioned yesterday), yes, it is solved by this.