Bump black version

[JimMadge]

✅ Checklist

• You have given your pull request a meaningful title (e.g. Enable foobar integration rather than 515 foobar).
• You are targeting the appropriate branch. If you're not certain which one this is, it should be develop.
• Your branch is up-to-date with the target branch (it probably was when you started, but it may have changed since then).
• You have marked this pull request as a draft and added '[WIP]' to the title if needed (if you're not yet ready to merge).
• You have formatted your code using appropriate automated tools (for example ./tests/AutoFormat_Powershell.ps1 -TargetPath <path to file or directory> for Powershell).

⤴️ Summary

Update the minimum black version in line with the changes made in source.
Updating versions in pyproject.toml this way should prompt hatch to update packages in your environments.

@jemrobinson I did the same sort of thing recently when Ruff went to 0.1.0. Not sure if the versions on those tools should be more restrictive. In some way I like that linting breaking prompts you to update those dependencies. It does mean that CI can break and not be your fault though 🤔.

🌂 Related issues

Related to #1718

🔬 Tests

hatch run lint:all from a fresh env.

[jemrobinson]

LGTM