Tracking issue for integrating a linter to PR builder

[mdumandag]

We should integrate some popular linters/code analysis tools to our PR builder to eliminate easy to find errors and maintain a consistent code style across the codebase. We should probably be using black + pylint, but that can be discussed.

Since we probably won't be able to fix all styling problems with one PR(possible, but would be really huge, hard to review PR), I created this issue to track the progress.

Not setting any milestone, as we can do it incrementally across multiple releases

[mdumandag]

The first part of this task is completed. We now check the code (apart from the autogenerated ones) using black.
See #284 #285 #286 #287 #288 #289 .

We will integrate pylint later.