Add UP009 to ruff
Author: cyyever
Pull request: yes

# What does this PR do?

<!--
Congratulations! You've made it this far! You're not quite done yet though.

Once merged, your PR is going to appear in the release notes with the title you set, so make sure it's a great title that fully reflects the extent of your awesome contribution.

Then, please replace this with a description of the change and which issue is fixed (if applicable). Please also include relevant motivation and context. List any dependencies (if any) that are required for this change.

Once you're done, someone will review your PR shortly (see the section "Who can review?" below to tag some potential reviewers). They may suggest changes to make the code even better. If no one reviewed your PR after a week has passed, don't hesitate to post a new comment @-mentioning the same persons---sometimes notifications get lost.
-->

<!-- Remove if not applicable -->

Fixes # (issue)


## Before submitting
- [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [ ] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#create-a-pull-request),
      Pull Request section?
- [ ] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link
      to it if that's the case.
- [ ] Did you make sure to update the documentation with your changes? Here are the
      [documentation guidelines](https://github.com/huggingface/transformers/tree/main/docs), and
      [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation).
- [ ] Did you write any new necessary tests?


## Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

<!-- Your PR will be replied to more quickly if you can figure out the right person to tag with @

 If you know how to use git blame, that is the easiest way, otherwise, here is a rough guide of **who to tag**.
 Please tag fewer than 3 people.

Models:

- text models: @ArthurZucker
- vision models: @amyeroberts, @qubvel
- speech models: @eustlb
- graph models: @clefourrier

Library:

- flax: @gante and @Rocketknight1
- generate: @zucchini-nlp (visual-language models) or @gante (all others)
- pipelines: @Rocketknight1
- tensorflow: @gante and @Rocketknight1
- tokenizers: @ArthurZucker
- trainer: @muellerzr and @SunMarc
- chat templates: @Rocketknight1

Integrations:

- deepspeed: HF Trainer/Accelerate: @muellerzr
- ray/raytune: @richardliaw, @amogkam
- Big Model Inference: @SunMarc
- quantization (bitsandbytes, autogpt): @SunMarc @MekkCyber

Documentation: @stevhliu

HF projects:

- accelerate: [different repo](https://github.com/huggingface/accelerate)
- datasets: [different repo](https://github.com/huggingface/datasets)
- diffusers: [different repo](https://github.com/huggingface/diffusers)
- rust tokenizers: [different repo](https://github.com/huggingface/tokenizers)

Maintained examples (not research project or legacy):

- Flax: @Rocketknight1
- PyTorch: See Models above and tag the person corresponding to the modality of the example.
- TensorFlow: @Rocketknight1

 -->


Comments:
Hi 👋, thank you for opening this pull request! The pull request is converted to draft by default. The CI will be paused while the PR is in draft mode. When it is ready for review, please click the `Ready for review` button (at the bottom of the PR page). This will assign reviewers and trigger CI.

cc @ydshieh @lysandrejik @arthurzucker @cyrilvallez this would change a lot of LOC in the codebase, but it would be nice for removing unnecessary lines and standardizing things like type hints. It would basically update Python conventions to 3.9 (and we we could set it to 3.10 after 3.9 reaches EOL). I'm a big fan of changes like replacing `str.format()` with f-strings. WDYT?

I am up for the reason to `standardizing things like type hints`. However:

- we will have to review every file, especially those with large changes (so not shown in the GitHub UI), for the security reason
  - or we have to run the command by ourselves
- ruff is still at version `0.x.x` and we pin the version(s) for quite some time before a next pin. So I personally don't feel it's really necessary to go this far for now. But ok.

Indeed, as @ydshieh mentionned, I would be much more confortable if someone internal was running the command and pushing the change, for security concerns

The only change I see here seem to be the removal of the `utf-8` line everywhere.
But in general, I'm very much in favor of switching to new type hints (i.e. using Python's built-in types, not Typing lib), and using f-strings instead of format

@Cyrilvallez I want to keep this PR easy to review by applying the simplest and most affecting fix. Other fixes should be added later.

I understand, but this has the opposite effect IMO -> we still need to review every line, and having separate PRs touching 100s of files each is a lot to review/parse for us. I think one of the best trade-offs may be to all agree on a format, then have someone internal running the command (this is nothing personal, but a basic security measure, I'm sure you can understand 🙂), then have that person adding you as a co-author of the PR, since this was your idea in the first place, so you deserve the contribution!

@Cyrilvallez That approach is more appropriate.