[Misc] fix collect_env version parse

[wangxiyuan]

The version parse in collect_env.py is not correct. The __version_tuple__ from setuptools_scm is a tuple like
(0,8,1), (0,8,1,dev86,ge588ac237) or (0,8,1,dev86,ge588ac237+d20250321). The length will never be 4. See: https://setuptools-scm.readthedocs.io/en/stable/usage/ which the length is not limited to 4.

We should pares the __version_tuple__ in a correct way. With this PR, the version will be parsed into some result:

1. if setuptools_scm is not working, the result will be N/A (dev)
2. if vllm is a tagged version, the result will be 0.8.1
3. if vllm is a dev version, the result will be 0.8.2.dev86+ge588ac237 (git_sha: e588ac237)
4. if vllm is a dev version with local changes, the result will be 0.8.2.dev86+ge588ac237.d20250321 (git sha: e588ac237, date: 20250321)

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

🚀

[houseroad]

Can we add some unittest?

[youkaichao]

Can we add some unittest?

unittest would be ideal, but it's complicated to test all the cases, e.g. released versions, dev versions, local installed versions, etc.

[wangxiyuan]

Fixed merge conflict