PyTorch XLA wrong device assignment with ellipsis 
Author: JingyaHuang
Pull request: yes

# What does this PR do?

Hi team, when trying to support some audio models in Optimum Neuron, I got some compilation failures due to a bug in PyTorch XLA: https://github.com/pytorch/xla/issues/6398.

[TL;DR] XLA will assign incorrect device (`lazy` instead of `xla`) when there is ellipsis (...), a swift workaround would be replacing all `...` with `:` to extract part of the tensor. Wonder if it's ok for transformers, so that Optimum Neuron can unblock audio tasks support without waiting for the fix in PyTorch XLA. Thanks! 

<details close>
<summary>Error log</summary>
<br>

```
E   AssertionError: sew, feature-extraction -> torch_xla/csrc/tensor.cpp:57 : Check failed: tensor.device().type() == at::kCPU (lazy vs. cpu)
E   *** Begin stack trace ***
E       tsl::CurrentStackTrace()
E       torch_xla::XLATensor::Create(at::Tensor const&, torch::lazy::BackendDevice const&)
E       torch_xla::bridge::GetOrCreateXlaTensor(at::Tensor const&, torch::lazy::BackendDevice const&)
E   
E       torch_xla::XLANativeFunctions::add(at::Tensor const&, at::Tensor const&, c10::Scalar const&)
E   
E       at::_ops::add_Tensor::redispatch(c10::DispatchKeySet, at::Tensor const&, at::Tensor const&, c10::Scalar const&)
E   
E   
E       at::_ops::add_Tensor::call(at::Tensor const&, at::Tensor const&, c10::Scalar const&)
E   
E   
E   
E   
E       _PyObject_FastCall_Prepend
E   
E   
E       PyNumber_Add
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E   
E       PyObject_Call
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E   
E       PyObject_Call
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E   
E       _PyObject_MakeTpCall
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E   
E       PyObject_Call
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E   
E       PyObject_Call
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E   
E       PyObject_Call
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E   
E       PyObject_Call
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E   
E       PyObject_Call
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E   
E       PyObject_Call
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E   
E       _PyEval_EvalFrameDefault
E       _PyFunction_Vectorcall
E       PyObject_Call
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E   
E       _PyEval_EvalFrameDefault
E       _PyFunction_Vectorcall
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E   
E       PyObject_Call
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E   
E       _PyObject_MakeTpCall
E       _PyEval_EvalFrameDefault
E       _PyFunction_Vectorcall
E       _PyEval_EvalFrameDefault
E       _PyFunction_Vectorcall
E       PyObject_Call
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E       _PyEval_EvalFrameDefault
E   
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E   
E       PyObject_Call
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E   
E       _PyEval_EvalFrameDefault
E       _PyEval_EvalCodeWithName
E       _PyFunction_Vectorcall
E       PyObject_Call
E       _PyEval_EvalFrameDefault
E   *** End stack trace ***
```

</details>


## Who can review?

Gently pinging @ArthurZucker and @amyeroberts

Comments:
The docs for this PR live [here](https://moon-ci-docs.huggingface.co/docs/transformers/pr_31912). All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.