Fix `bad_words_ids` not working with sentencepiece-based tokenizers
Author: ngoquanghuy99
Pull request: yes

# What does this PR do?
This fixes the problem models using sentencepiece-based tokenizers can not prevent bad words when decoding. 
For sentencepiece-based tokenizers like T5Tokenizer, when creating `bad_words_ids` from `bad_words`, `add_special_tokens` must be set to False.

## Code to reproduce
```python
from transformers import T5Tokenizer, AutoModelForCausalLM, T5ForConditionalGeneration

tokenizer = T5Tokenizer.from_pretrained("t5-small", use_fast=False)
model = T5ForConditionalGeneration.from_pretrained("t5-small")


bad_words = ["my", "will", "My", "you", "are", "I", "You", "it"] # words should not be generated 
bad_words_ids = tokenizer(bad_words, add_prefix_space=True, add_special_tokens=False).input_ids # get bad words ids 

input_context = "You are my friend"
# encode input context
input_ids = tokenizer(input_context, return_tensors="pt").input_ids
outputs = model.generate(input_ids=input_ids, max_length=20, do_sample=True, bad_words_ids=bad_words_ids, num_return_sequences=3)
gen_texts = tokenizer.batch_decode(outputs, skip_special_tokens=True)

```
<!--
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 -->


## Who can review?
@patrickvonplaten @LysandreJik 

<!-- 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._

Hey @ngoquanghuy99, 

That's a great fix - thanks a lot for diving into this :-) 
Could you run `make style` once so that the `check_code_quality` test goes green?