[Bugfix] Initialize attention bias on the same device as Query/Key/Value for QwenVL Series

[LouieYang]

Similar issue as #13468 where the attention bias in vLLM's xformers backend is currently initialized on the default device, rather than the device of the Q/K/V tensors.

The #13468 workaround doesn't quite solve the problem for QwenVL series when vLLM is used in conjunction with libraries like trl for GRPO training.

The cuda device mismatched issue still exists for xformer backend.

[rank0]: ValueError: Attention bias and Query/Key/Value should be on the same device

This PR solve cuda device mismatch problem for QwenVL Series

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

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 either: Add ready label to the PR or enable auto-merge.

🚀

[Isotr0py]

Can you please address the pre-commit linting errors?