Add type hints Yoso Pytorch
# What does this PR do?
Add missing Type Hints for Yoso pytorch 
#16059 
<!--
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
- [x] 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?
- [x] 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.
@Rocketknight1 



_The documentation is not available anymore as the PR was closed or merged._<|||||>Hello @Rocketknight1 I finished with yoso pytorch. I don't know why this pull request contain commits from previous pull request <|||||>I updated the file after running make fixup and now it passed all checks<|||||>@F02934 Thanks for this! Don't panic about the other files being changed - if you want, you should be able to fix that by pulling the latest version of main, then rebasing your PR branch onto main and finally force-pushing. I don't think it should cause any problems if you don't, though, except for cosmetic ones in the Github interface. 

Also, your type hints look good, but would you be willing to annotate the other model classes in the file too (the ones starting with `YosoFor...`)?<|||||>@Rocketknight1 thank you! I will just leave as it is because I'm afraid to mess up. 
I will finish yoso tomorrow!<|||||>Hi @Rocketknight1 I checked the `YosoFor` but they were already done. On [this Colab notebook](https://colab.research.google.com/drive/1EvZTslb50yfRqIcXjCZFrbod4HrPdA0G?usp=sharing) you shared I checked the missing type hints for Yoso pytorch and only "YosoForQuestionAnswering" and "YosoForTokenClassification" were missing which I added in this PR. So I think everything done. But correct me if I'm wrong!<|||||>Sorry, you're completely right! The type hints for Yoso are ready to go.

I investigated the extra Italian documentation added by this PR, though - I think the problem there is that your PR branch was created as a branch of an existing PR branch, which was probably working on translation fixups. As a result, it sort of carries changes from both branches!

The simplest way to fix this would be to close this PR, make a new branch starting from `main` this time, and then just copy the changes in `modeling_yoso.py` to that branch, and finally open a PR from that new branch. Is that okay? I'll try to review it quickly if you do, since I've already checked your type hints, lol<|||||>@Rocketknight1 alright. I will do it right now!