Clean up deprecation warnings
The deprecation spring cleaning mentioned in #19371

Notes:
Changed some strings in tests to raw strings, which will change the literal content of the strings as they are fed into whatever machine handles them.
Test cases for past in the past/past_key_values switch changed/removed due to warning of impending removal
Most of the warnings defined and thrown by transformers functions were left alone

# 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).
- [x] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#start-contributing-pull-requests),
      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:

- albert, bert, xlm: @LysandreJik
- blenderbot, bart, marian, pegasus, encoderdecoder,  t5: @patrickvonplaten, @patil-suraj
- longformer, reformer, transfoxl, xlnet: @patrickvonplaten
- fsmt: @stas00
- funnel: @sgugger
- gpt2: @patrickvonplaten, @LysandreJik
- rag: @patrickvonplaten, @lhoestq
- tensorflow: @LysandreJik

Library:

- benchmarks: @patrickvonplaten
- deepspeed: @stas00
- ray/raytune: @richardliaw, @amogkam
- text generation: @patrickvonplaten
- tokenizers: @n1t0, @LysandreJik
- trainer: @sgugger
- pipelines: @LysandreJik

Documentation: @sgugger

HF projects:

- datasets: [different repo](https://github.com/huggingface/datasets)
- rust tokenizers: [different repo](https://github.com/huggingface/tokenizers)

Examples:

- maintained examples (not research project or legacy): @sgugger, @patil-suraj
- research_projects/bert-loses-patience: @JetRunner
- research_projects/distillation: @VictorSanh

 -->

_The documentation is not available anymore as the PR was closed or merged._<|||||>@Davidy22 Thanks for opening this PR and all of the fixes! 💪 

Just taking a look now. It would really helpful as a reviewer, and for future reference if you could give a quick summary of the deprecation warnings you tackled.

As a quick note regarding `PIL.Image.XXX` -> `PIL.Image.Resampling.XXX`, these changes might be breaking (c.f. [open transformers issue](https://github.com/huggingface/transformers/issues/19569) and [related PR in diffusers](https://github.com/huggingface/diffusers/pull/788) as it requires `Pillow>=9.1.0` which is not currently enforced. @sgugger What is the typical strategy for handling dependancy version updates? <|||||>Thanks for pointing this out Amy! In this case, Pillow 9.1.0 is too recent to be pinned as a minimum version (our general rule of thumb is to provide a support for 2 years and this is only from April). So we will need to move those objects to our `image_utils.py` where we can do some checks like:
```py
if version.parse(version.parse(PIL.__version__).base_version) >= version.parse("9.1.0"):
    # Define enum using `PIL.Image.Resampling`
else:
    # Define enum using `PIL.Image`
```

As for the actual enum, we could name it `PILImageResampling`?<|||||>Oh whoops I probably should have taken a couple more notes, I only wrote down a couple of things that stood out as things that'd functionally change something. Summary from re-skimming through the listed changes:

- np types swapped with equivalent python default types
- PIL Resampling options switched to the new recommended location in the PIL library
- Some strings with non-python escapes changed to r strings.
- dict_type -> dict parameter in dictionary.Dictionary
- Usages of past changed to past_key_values
- topk -> top_k<|||||>Added PILImageResampling, dealt with some funky import issues in one file that weren't happening in any of the other files, don't know why specifically the flava test file would have issues importing from image_utils, hoping it's not some thing that actually also happens in other files but doesn't get surfaced because it's not covered or something