[Bugfix] Ignore ray reinit error when current platform is ROCm or XPU

[HollowMan6]

Just like the else branch, we should also add ignore_reinit_error=True when calling ray.init, so that the reinit error can be ignored if vLLM is called by another program and ray has already been initialized:

 File "vllm/vllm/entrypoints/llm.py", line 213, in __init__
   self.llm = vllm.LLM(*args, **kwargs)
              ^^^^^^^^^^^^^^^^^^^^^^^^^
 File "vllm/vllm/utils.py", line 1024, in inner
   return fn(*args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^
   self.llm_engine = self.engine_class.from_engine_args(
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 File "vllm/vllm/engine/llm_engine.py", line 580, in from_engine_args
   executor_class = cls._get_executor_cls(engine_config)
 File "vllm/vllm/engine/llm_engine.py", line 555, in _get_executor_cls
   initialize_ray_cluster(engine_config.parallel_config)
 File "vllm/vllm/executor/ray_utils.py", line 237, in initialize_ray_cluster
   ray.init("auto")
          ^^^^^^^^^^^^^^^^^^^^^
RuntimeError: Maybe you called ray.init twice by accident? This error can be suppressed by passing in 'ignore_reinit_error=True' or by calling 'ray.shutdown()' prior to 'ray.init()'.

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.
Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can do one of these:

• Add ready label to the PR
• Enable auto-merge.

🚀

[youkaichao]

LGTM