Add the XPU device check for pipeline mode
Author: yuanwu2017
Pull request: yes

When setting xpu device for pipeline, It needs to use is_torch_xpu_available to load ipex and determine whether the device is available.

# 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.
-->



## Before submitting
- [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [x] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/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.
- [x] 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.

<!-- 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:
Hey! Feel free to ping me for a review when this is ready! 

Hi  @ArthurZucker,
I tested the failed run_tests case in my local machine, but I got following warning. I think the case failure is not caused by my patch. Do you know how to run the case correctly? Thanks a lot.

```
(upstream) [yuanwu@skyocean transformers]$ pytest tests/test_modeling_flax_common.py
============================================================================================ test session starts =============================================================================================
platform linux -- Python 3.9.18, pytest-7.4.0, pluggy-1.0.0
rootdir: /mnt/disk4/yuanwu/workspace/transformers
configfile: pyproject.toml
plugins: anyio-3.5.0, xdist-3.5.0, timeout-2.2.0, hypothesis-6.92.2, dash-2.14.2
collected 0 items

============================================================================================== warnings summary ==============================================================================================
../../../../../home/yuanwu/.conda/envs/upstream/lib/python3.9/site-packages/_pytest/config/__init__.py:1373
  /home/yuanwu/.conda/envs/upstream/lib/python3.9/site-packages/_pytest/config/__init__.py:1373: PytestConfigWarning: Unknown config option: doctest_glob

    self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
============================================================================================= 1 warning in 0.38s =============================================================================================
```

@ArthurZucker I think the patch is ready. Please review. Thanks.

@ArthurZucker  Please help to review.

Yes sorry for the delay! 

Hi @ArthurZucker  
Done for raising error when device is not available.

Thanks @ArthurZucker 
Done.

Thanks, let's make sure the CI is green!

@yuanwu2017 There was a fix merged into main which resolves the currently failing tests - could you rebase to include these and trigger an new CI run?