Update black to non pre-release version

[Galileo-Galilei]

Motivation and Context

Upgrade black to 22.1.0 consistently with kedro-org/kedro#1327.

How has this been tested?

• I have run black on the entire repo. Notice that some files return an error because of the jinja tags which are not valid python.
• I also manually created a project fom each starter and run black and one single file is sometimes modified: the setup.py because the length of line with the entry point depends on the length of the project, which we don't know in advance. There are not other modifcation.
• As for the original repo, I did NOT change black version in test_requirements.txt. Should I?

Checklist

• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Assigned myself to the PR -> I don't have the right to do it
• Added tests to cover my changes -> should I create a test to check if the template is "black valid"? What should I do for the lines which are splitted depending on the length of the project name?

[antonymilne]

Thanks very much for doing this @Galileo-Galilei! And especially for your diligent testing.

In response to your points:

• yes please to updating test_requirements.txt - I don't think it will have any practical impact but will just help keep things consistent
• I've assigned you to the PR. That's weird you weren't able to - I guess we'll need to check the repo permissions
• no need to create a test to check that files are correctly formatted because we actually already have one which automatically does exactly what you did manually: https://github.com/kedro-org/kedro-starters/blob/main/features/lint.feature. The issue with line breaks depending on the length of cookiecutter variables isn't a problem (hopefully) because when we do kedro new for each starter we use a config file to provide values for the cookiecutter variables: https://github.com/kedro-org/kedro-starters/blob/main/features/steps/run_steps.py#L9

The problem here is that for some reason your PR hasn't triggered any of our CI checks. You should be seeing something like this:

I think @MerelTheisenQB might know what the solution is here to get the checks to execute on this PR.

Also N.B. @lorenabalan I advised that this PR should go into your 0.18.0 branch since it relies on the recently bumped click version requirement, which is only in develop. Hope that's right.

[antonymilne]

Forget what I said about the CircleCI jobs actually - we just hadn't enabled them to run on forked PRs. It's been enabled and I've done a PR to trigger them now 😄

[merelcht]

LGTM! 👍 Just don't forget to update test_requirements.txt 🙂