Ruff formatter

[Kilo59]

Adopt the ruff formatter and drop black

https://astral.sh/blog/the-ruff-formatter

[gx-cla-bot]

A new contributor, HUZZAH! Welcome and thanks for joining our community. In order to accept a pull request we require that all contributors sign our Contributor License Agreement. We have two different CLAs, depending on whether you are contributing to GX in a personal or professional capacity. Please sign the one that is applicable to your situation so that we may accept your contribution:

Individual Contributor License Agreement v1.0
Software Grant and Corporate Contributor License Agreement v1.0

Once you have signed the CLA, you can add a comment with the text @cla-bot check and the bot will update the PR status!

Please reach out to the #gx-community-support channel, on our Slack if you have any questions or if you have already signed the CLA and are receiving this message in error.

Users missing a CLA: pre-commit-ci[bot]

[wookasz]

Let's figure out which tools we'd like to use, and use them uniformly across our repositories to avoid cognitive overhead.

[Kilo59]

@wookasz
I'm proposing that we switch to using ruff format uniformly.
Assuming no one objects and nothing unexpected pops up in the attempt to adopt it here.
Do you have a specific objection to switching to the ruff formatter?

Developers will likely not even notice the difference.

1. If developers have the pre-commit hooks installed the formatting is applied automatically when committing code.
2. If developers are using invoke fmt the only difference is invoke calls ruff format instead of black
3. If developers don't use either and misformat something the pre-commit CI will push a fix to the branch automatically.

AFAIK the only case where a developer workflow would change is if they are manually running black from the terminal after every change.

[Kilo59]

Using a new version of poetry here.