[Misc][Gaudi] Avoid torch.compile and enable lazy collectives by default for HPU lazy backend

[kzawora-intel]

Similar to #10747, but applied specifically to PT HPU lazy backend. While PyTorch for Gaudi has torch.compile support, it currently needs to be enabled explicitly, and best performance is achieved with HPUGraphs instead. This patch disables torch.compile for PT lazy mode and HPUGraphs (HPU execution modes for reference: https://docs.vllm.ai/en/latest/getting_started/gaudi-installation.html#execution-modes), and leaves it on for PT eager/torch.compile mode. Additionaly, it automatically sets the flag for enabling lazy collectives required in multi-HPU inference with HPUGraphs, fixing frequently reported RuntimeError: collective nonSFG is not supported during hpu graph capturing error.

[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.

🚀

[jikunshang]

LGTM!

[mgoin]

This seems reasonable to me cc @youkaichao to sign off before merge

[youkaichao]

LGTM