update the arguments `add_prefix_space` and `trim_offsets` in `backend_tokenizer.post_processor` of `RobertaTokenizerFast`
# What does this PR do?

Roberta's tokenizer fast has `add_prefix_space` and `trim_offsets` as arguments. It seems to me that these last 2 arguments should be updated accordingly in the post processor `RobertaProcessing` of its `backend_tokenizer`. 

This PR proposes to automate this update with a strategy similar to the update of the `pre_tokenizer` done inside the `__init__` of `GPT2TokenizerFast` (from which `RobertaTokenizerFast` inherits).

It is the issue #14305 that allowed me to notice that this update was not done when changing `add_prefix_space` or `trim_offsets`.

I would ideally like to wait until I have an opinion on [this issue](https://github.com/huggingface/tokenizers/issues/843) on the Tokenizers library before merging this PR.

Edit: So I had the confirmation that there was a bug on the Tokenizer side, which was solved in [this PR](https://github.com/huggingface/tokenizers/pull/844) which confirms my understanding of the `RobertaTokenizerFast` component.
<!--
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 -->



## 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. Maybe @LysandreJik, @sgugger what do you think of this change? (and in particular of the fact that the behavior will not be entirely satisfactory before the fix on the tokenizers side is released)

<!-- 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

 -->

Is this leveraging PR https://github.com/huggingface/tokenizers/pull/844 that was just merged in `tokenizers` ? I believe it isn't part of a version yet, right?

Or is this meant as a patch on top of the current tokenizers version?<|||||>@LysandreJik, you do raise an important point.

This PR only proposes to reflect the choices of the user on the arguments `add_prefix_space` and `trim_offsets` on the `backend_tokenizer`. Before this modification the `add_prefix_space` and `trim_offsets` arguments were not changed in the post_processors while they are in the pre_tokenizer (in the `__init__` of the GPT2 tokenizer), which causes problems.

Nevertheless, the investigation of this problem allowed us to identify a problem on the side of the Tokenizers library that has been solved in the PR you mention. As long as there is no new version of Tokenizers, this problem will also affect the transformers library.

To sum up,  this PR just aligns the arguments chosen between the pre_tokenizer and the post_processor components of the tokenizer.<|||||>To complete this PR, I created [a new branch with a new test that shows the behavior that will remain incorrect](https://github.com/SaulLu/transformers/pull/1) until we can use a new version of `Tokenizers` that includes [this commit](https://github.com/huggingface/tokenizers/pull/844). 

cc @LysandreJik and @sgugger for visibility