Fix typing about next_beam_tokens and next_beam_indices
# What does this PR do?

Looking at source code they seem to be int not float?

<!--
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).
- [ ] 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:

- text models: @ArthurZucker and @younesbelkada
- vision models: @amyeroberts and @NielsRogge
- speech models: @sanchit-gandhi

Library:

- flax: @sanchit-gandhi
- generate: @gante
- pipelines: @Narsil
- tensorflow: @gante and @Rocketknight1
- tokenizers: @ArthurZucker
- trainer: @sgugger

Integrations:

- deepspeed: @stas00
- ray/raytune: @richardliaw, @amogkam

Documentation: @sgugger and @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: @sanchit-gandhi
- PyTorch: @sgugger
- TensorFlow: @Rocketknight1

 -->

The docs for this PR live [here](https://moon-ci-docs.huggingface.co/docs/transformers/pr_20832). All of your documentation changes will be reflected on that endpoint.<|||||>Please make sure to run `make style` on your branch so that the quality tests pass.
cc @gante for review.<|||||>Sure, I will do it soon together with another PR in https://github.com/huggingface/transformers/issues/20820<|||||>Please have each of your PR focused on one thing. We don't want to group changes that are not linked to each other in the same PR :-)<|||||>Sure, I mean file two PRs but do the *work* in one single time slot of mine ;)

No worries, I am experienced to make PRs (e.g. to Google Flutter https://github.com/flutter/flutter/pulls?q=is%3Apr+author%3Afzyzcjy)<|||||>This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread.

Please note that issues that do not follow the [contributing guidelines](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md) are likely to be ignored.<|||||>bump, will do it when having time<|||||>Hi, I wonder what version of `black` is required? I have tried:

```
(dev-transformers) ➜  transformers git:(patch-1) python3 -m black -- examples tests src utils           
Skipping .ipynb files as Jupyter dependencies are not installed.
You can fix this by running ``pip install black[jupyter]``
reformatted src/transformers/utils/model_parallel_utils.py
reformatted tests/models/xlm_prophetnet/test_modeling_xlm_prophetnet.py
reformatted src/transformers/models/layoutlmv3/tokenization_layoutlmv3.py
reformatted src/transformers/models/markuplm/tokenization_markuplm.py
reformatted src/transformers/models/layoutlmv2/tokenization_layoutlmv2.py
reformatted examples/research_projects/lxmert/modeling_frcnn.py
reformatted examples/research_projects/visual_bert/modeling_frcnn.py
reformatted src/transformers/models/prophetnet/modeling_prophetnet.py
reformatted src/transformers/models/xlm_prophetnet/modeling_xlm_prophetnet.py
reformatted src/transformers/models/reformer/modeling_reformer.py
reformatted src/transformers/tokenization_utils_base.py

All done! ✨ 🍰 ✨
11 files reformatted, 2138 files left unchanged.
```

and so on. It is changing formats for a dozen of files that I did not touch, such as:

![image](https://user-images.githubusercontent.com/5236035/213868622-34147495-af56-4971-9a33-034ab81c7607.png)
![image](https://user-images.githubusercontent.com/5236035/213868628-1f9884c8-4b54-4862-9a27-b2c0fbdf1488.png)
![image](https://user-images.githubusercontent.com/5236035/213868632-3c24ef72-e74b-4fa4-923c-48c60e11c7ab.png)
![image](https://user-images.githubusercontent.com/5236035/213868664-61ac3b12-03d7-49f2-a00c-4d05d8b196d8.png)

(P.S. I did not run `make style` but instead invoke that command directly because my `black` on PATH has a little conflict. I have followed https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md and create a brand new conda environment and install via pip)<|||||>@fzyzcjy We use black 22.3 (see [here](https://github.com/huggingface/transformers/blob/e1cd78634ae4ba2b0a3d548bd6663c08765a8b4d/setup.py#L101))<|||||>Hmm it is the correct version

```
python -m black --version
python -m black, 22.3.0 (compiled: yes)
```<|||||>@fzyzcjy Suggestion: revert to the first commit (which only touches 2 lines), run `make fixup` (which only touches modified files), then force commit the result :)<|||||>This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread.

Please note that issues that do not follow the [contributing guidelines](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md) are likely to be ignored.