Apply black

[utnapischtim]

❤️ Thank you for your contribution!

Description

This PR migrates the whole repository to be formatted by black by applying following shell command to the whole repository:

find -name '*.py' -exec black {} \;

Further, the PR uses the .git-blame-ignore-revs file to ignore "apply black to the whole codebase" commit if git blame is used. It works also on github. As the introducing_black_to_your_project suggests i did also git config --global blame.ignoreRevsFile .git-blame-ignore-revs to ignore the commit on your pc. With --global it has to be done only once.

Also, the PR moved the pytest.ini to setup.cfg to make the setup.cfg the only configuration file wherever possible.

This PR uses pytest-black to check if black was used as the formatting tool. the --black was added to the addopts of the pytest configuration.

I would like to discuss with this commit whether we want to use pylint. I explicitly made the changes with a single commit so it's clear what changes are required for this repository.

Checklist

Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

• I'm aware of the code of conduct.
• I've created logical separate commits and followed the commit message format.
• I've added relevant test cases.
• I've added relevant documentation.
• I've marked translation strings (for relevant code).
• I've followed the CSS/JS and React guidelines (for relevant code).
• I've followed the web accessibility guidelines (for relevant code).
• I've followed the user interface guidelines (for relevant code).
• I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
• I've NOT included third-party code (copy/pasted source code or new dependencies).

Third-party code

If you've added third-party code (copy/pasted or new dependencies), please reach out to an architect.

Reminder

By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

1. You license your contribution under the same terms as the current repository’s license.
2. You agree that you have the right to license your contribution under the current repository’s license.