Feature request: support more than device keyword arg when calling .to() on BatchEncoding
### Feature request

I see that the `.to()` [method](https://github.com/huggingface/transformers/blob/f1660d7e23d4432513fe060bde4f9b7b29f05204/src/transformers/tokenization_utils_base.py#L751) of `BatchEncoding` returned by tokenizers only supports the `device` keyword argument.

However, the `BatchFeature` returned by image processors/audio feature extractors supports [more keyword arguments](https://github.com/huggingface/transformers/blob/f1660d7e23d4432513fe060bde4f9b7b29f05204/src/transformers/feature_extraction_utils.py#L187), most importantly `dtype`.

### Motivation

This is handy as it allows to do:
```
from transformers import ViTImageProcessor
import torch
from PIL import Image
import requests

processor = ViTImageProcessor()

url = "http://images.cocodataset.org/val2017/000000039769.jpg"
image = Image.open(requests.get(url, stream=True).raw)

encoding = processor(image, return_tensors="pt").to(device="cuda", dtype=torch.float16)

for k,v in encoding.items():
    print(k,v.dtype)
```
which returns
```
pixel_values torch.float16
```


### Your contribution

I could submit a PR but if anyone has the bandwidth for this, would be great to add it :D 
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.<|||||>@NielsRogge @amyeroberts Hey I am interested on working on this issue. It is my first one so I'll need some guidance. I'll try my best and ping you if i need help!<|||||>@amannagarkar Great! :D Feel free to ask questions on the PR once it's opened! <|||||>I can help with this too @amyeroberts
Would that be okay? @amannagarkar <|||||>@Rishab26 I am already working on the issue! I will let you know in a couple of days? I am testing the code for errors and will open a pr shortly! <|||||>@amannagarkar Sure, no worries. Happy to collaborate together too. I've taken a shot at it 👍