Add more pre-commit hooks

[ioggstream]

I expect

• all the pre-commit hooks we have in https://github.com/par-tec/base-cookiecutter

[ilovelinux]

Honestly, I don't like the idea to mix-up Python-related things with non-Python related things.

When I visit python-cookiecutter, I'd like to have all Python-related instruments to bootstrap a Python project. I may still need some of the things in base-cookiecutter, but keeping them aligned is an hassle and we know that doing it by hand can't be a solution.

What if instead:

• Use https://github.com/par-tec/base-cookiecutter for generic pre-commit hooks
• Use this repository for python-related pre-commit hooks
• Nothing should be in both repositories (I'm talking about components, we can still have same filenames)
• Add a comment inside this repository's pre-commit configuration about getting more hooks in base-cookiecutter

Then:

• We do not duplicate the pre-commit configuration for base hooks (two points of truth for two completely different things)
• This repository is going to be easier to maintain

Extras:

• We may apply this logic also for the other components in this repository. (e.g. .yamllint)

Alternatives:

• We may create a cronjob CI to create PR if some components of this repository are not aligned with base-cookiecutter
• We may create a script to generate the final python-cookiecutter
• We may create a CI that runs on master and creates an artifact with the final python-cookiecutter
• We may create another repository and a CI that merges this repository and base-cookiecutter together
• We may create hooks from this repository and reference them in our projects (harder, we would need to make releases etc..)