fix: data2vec-vision Onnx ready-made configuration.
Author: NikeNano
Pull request: yes

# What does this PR do?

This PR adds the missing config for the ONNX data2vec  config for images. It is stated in the [docs](https://huggingface.co/docs/transformers/serialization) that there is a default config for the facebook/data2vec-vision-base but this is currently not working and gives 

```
...
 File "/transformers/src/transformers/onnx/features.py", line 486, in get_supported_features_for_model_type
    raise KeyError(
KeyError: "data2vec-vision is not supported yet. Only ['albert', 'bart', 'beit', 'bert', 'big-bird', 'bigbird-pegasus', 'blenderbot', 'blenderbot-small', 'bloom', 'camembert', 'codegen', 'convbert', 'convnext', 'data2vec-text', 'deberta', 'deberta-v2', 'deit', 'detr', 'distilbert', 'electra', 'flaubert', 'gpt2', 'gptj', 'gpt-neo', 'ibert', 'layoutlm', 'layoutlmv3', 'levit', 'longt5', 'marian', 'mbart', 'mobilebert', 'mobilevit', 'm2m-100', 'perceiver', 'resnet', 'roberta', 'roformer', 'squeezebert', 't5', 'vit', 'xlm', 'xlm-roberta', 'yolos'] are supported. If you want to support data2vec-vision please propose a PR or open up an issue."
```

to recreate using docker: 

```bash
docker run -it huggingface/transformers-all-latest-gpu /bin/bash
```

```python
python3 -m transformers.onnx --model=facebook/data2vec-vision-base  onnx/
```

Should I create an issue for this and link to it?

Thanks for the help!

<!--
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.
- [x] 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).
- [x] 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:
_The documentation is not available anymore as the PR was closed or merged._

@lewtun @LysandreJik  maybe you could take a look or point me to the correct person. Thanks!

cc @michaelbenayoun @JingyaHuang as Lewis is off for a few weeks :)

What is the best practice in this case for the test that failed? As far as I an see it is not related to the changes? How do I rerun it? @JingyaHuang thanks!

> What is the best practice in this case for the test that failed? As far as I an see it is not related to the changes? How do I rerun it? @JingyaHuang thanks!

Can you rebase your branch with the main branch of transformers and re-launch the failed test?

LGTM!
Have you ran this command?
```
RUN_SLOW=1 pytest tests/onnx/test_onnx_v2.py 
```
I was able to export the model on your branch, with your command, but I want to make sure all the tests pass before merging.

> LGTM! Have you ran this command?
> 
> ```
> RUN_SLOW=1 pytest tests/onnx/test_onnx_v2.py 
> ```
> 
> I was able to export the model on your branch, with your command, but I want to make sure all the tests pass before merging.

I missed this but will run this tomorrow and fix it if it needs to!