Pylint alerts corrections as part of an intervention experiment

[evidencebp]

Is your feature request related to a problem? Please describe.
Pylint alerts are correlated with tendency to bugs and harder maintenance.
I'd like to conduct a software engineering experiment regarding the benefit of Pylint alerts removal.
The experiment is described here.

In the experiments, Pylint is used with some specific alerts, files are selected for intervention and control.
After the interventions are done, one can wait and examine the results.

Your repository is expected to benefit from the interventions.
I'm asking for your approval for conducting an intervention in your repository.

See examples of interventions in stanford-oval/storm, gabfl/vault, and coreruleset/coreruleset.

Describe the solution you'd like

You can see the planed interventions
The plan is to do 36 interventions in 31 files
The interventions will be of the following types:
broad-exception-caught: 2
line-too-long: 11
simplifiable-if-expression: 13
too-many-branches: 7
too-many-nested-blocks: 1
unnecessary-pass: 2

Since the plan is not too big, I implemented it already.
I'll submit a PR to your review, hoping that you will like it.
Please tell me if modifications are needed.

Describe alternatives you've considered
You can leave the code as is.

Your Environment (please complete the following information):

• OS: Windows 10
• Python version: Python 3.10

Additional context

[evidencebp]

See the PR

[evidencebp]

Sorry, the bioconda PR reference is a mistake, please ignore it.