Don't call the venv vllm

[hmellor]

Calling your virtual environment vllm when it is created in your pwd, as it is with uv venv, will definitely lead to mysterious import errors.

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

🚀

[WoosukKwon]

random idea: Can we just rename it to my_vllm or something like that?

[hmellor]

Since the venvs created by uvare local to each project, I always find myself using the default name. Especially because this is in most .gitignore files I can create it inside the repo with no issues.