Update bros checkpoint
Author: jinhopark8345
Pull request: yes

# 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 -->

Update [Bros](https://arxiv.org/abs/2108.04539) checkpoint.

The `naver-clova-ocr/bros-base-uncased` checkpoint has `bbox_projection` layer in `BrosEmbeddings` class but this layer is moved to `BrosBboxEmbeddings` class. And users are expected to use `jinho8345/bros-base-uncased` checkpoint instead of `naver-clova-ocr/bros-base-uncased`.

* `naver-clova-ocr/bros-base-uncased` : original pretrained checkpoint from naver-clova-ocr
* `jinho8345/bros-base-uncased` :  weights renamed version from `naver-clova-ocr/bros-base-uncased` using [conversion script](https://github.com/huggingface/transformers/blob/main/src/transformers/models/bros/convert_bros_to_pytorch.py)



## 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/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. - https://github.com/huggingface/transformers/pull/23190#issuecomment-1725882060
- [ ] 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.

@ydshieh 

<!-- 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
- speech models: @sanchit-gandhi
- graph models: @clefourrier

Library:

- flax: @sanchit-gandhi
- generate: @gante
- pipelines: @Narsil
- tensorflow: @gante and @Rocketknight1
- tokenizers: @ArthurZucker
- trainer: @muellerzr and @pacman100

Integrations:

- deepspeed: HF Trainer/Accelerate: @pacman100
- ray/raytune: @richardliaw, @amogkam
- Big Model Inference: @SunMarc
- quantization (bitsandbytes, autogpt): @SunMarc and @younesbelkada

Documentation: @stevhliu and @MKhalusova

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: See Models above and tag the person corresponding to the modality of the example.
- TensorFlow: @Rocketknight1

 -->


Comments:
The docs for this PR live [here](https://moon-ci-docs.huggingface.co/docs/transformers/pr_26277). All of your documentation changes will be reflected on that endpoint.

Is there a reason why we did not go with creating new repos with `naver-clova-ocr/bros-base-uncased-hf` instead of a custom repo? 

> Is there a reason why we did not go with creating new repos with `naver-clova-ocr/bros-base-uncased-hf` instead of a custom repo?

No reason at all. I also considered that it would be more reliable to use checkpoint that huggingface controls.

I'll ask for the models to be moved if that is okay with you? 


I am not sure if @jinhopark8345 can move repo to `naver-clova-ocr`. Even for us, we will need `naver-clova-ocr` to approve I think.

Sorry merged this PR without waiting core maintainers' approval.

@ArthurZucker I can not move the repo to `naver-clova-ocr` as @ydshieh assumed. And I am sorry that I didn't mention about my concern earlier, @ydshieh. 

I'll ask for the checkpoints to be move then 😉