Put `load_image` function in `image_utils.py` & fix image rotation issue
Author: mishig25
Pull request: yes

# What does this PR do?
1. Put `load_image` function in `image_utils.py`
2. Encountered and fixing `PIL.Image.open is rotating jpeg images` https://github.com/python-pillow/Pillow/issues/4703

<!--
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/master/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/master/docs), and
      [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/master/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

 -->


Comments:
Which version of Pillow are you using ? transformers doesn't specify a version.

> Pillow 8.0.0 is automatically rotating images upon .open based on EXIF Orientation tag.
Also probably a good time to remove code duplication here.

```
>>> PIL.__version__
'8.3.1'
```

also, I get rotated mask results from Inference API, which is how I encountered this issue

I think we need to add some form of test to expose the necessity for this as it's not trivial and might be fixed upstream (as it claims to be).

So we need an image file (can be in `hf-internal-testing` with said exif data) and show that the loading is improper (this test can be entirely separated from the pipeline, here we're testing the `load_image` method, so we can have a separate class of test for this that focuses on specifically this feature.

@narsil Should I use this opportunity to address ([src](https://github.com/huggingface/transformers/pull/13828#discussion_r721202947)):
> It might be time to create a utils file and put it in there maybe so we can just reuse this code all the time and test it separately. (it should be another PR, just mentioning it here)

If so, should I just make `load_image` a method of  [ImageFeatureExtractionMixin](https://github.com/huggingface/transformers/blob/83e5a10603ca902c266e40fc98a01dd8a9b04ac4/src/transformers/image_utils.py#L33-L36) & make Vision pipelines inherit `ImageFeatureExtractionMixin`?

Just put the function outside the class, it's a simple function it doesn't deserve a mixin.

In another branch I added `src/transformers/audio_utils.py` to host `ffmpeg_read` for instance.

(It's the first thing that popped in mind in terms of location, maybe we can find a better location ultimately, here goal is just to reduce repetition)

@Narsil please feel free to re-review this PR. I've added the changes as suggested.
Specifically, this test case
https://github.com/huggingface/transformers/blob/dd6d891d90bf789b18f45e901d52d163d7f822a3/tests/test_image_utils.py#L436-L442

Before merging, there seems to be a few tests failing linked to your PR!

@LysandreJik thanks for notifying about the failing tests. Solved! There was an issue with the `hf-internal-testing/fixtures_image_utils` I've created