Improving pylint formatting

Currently we still have lots of excluded cases for pylint, we should slowly fix (most of) them

• unspecified-encoding
• no-name-in-module
• too-many-arguments
• too-many-locals
• too-many-lines
• too-many-statements
• too-many-branches
• too-many-nested-blocks
• too-many-instance-attributes
• duplicate-code
• too-few-public-methods
• invalid-name (related issue #167 (closed))
• logging-fstring-interpolation (fixed in !582 (merged))

The following options should be kept

• no-member: should be kept, since lots of false positives)
• wrong-import-order: due to the logging issues from tensorflow, which always need to come first as well as the logging for umami