[Hardware][AMD]: Replace HIPCC version with more precise ROCm version

[hj-wei]

Hi all, Ifound that the representation of the ROCm version is somewhat unclear. For instance, in the case of the current ROCm version 6.2.0, the version specified in setup.py is 624, which corresponds to the HIPCC version. To represent the ROCm version more accurately, I opted to utilize the version representation provided in the rocm-core package, which retrieves the ROCm version through the available version query interfaces.
see https://github.com/ROCm/rocm-core/blob/d11f5c20d500f729c393680a01fa902ebf92094b/rocm_version.cpp#L21

On the other hand, the HIPCC version can be directly obtained via torch.version.hip.

You can also directly use the ROCM_VERSION information provided by the torch package，https://github.com/pytorch/pytorch/blob/cf76c05b4dc629ac989d1fb8e789d4fac04a095a/torch/utils/cpp_extension.py#L244

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

🚀

[hongxiayang]

LGTM. Please address the ruff/yapf failures.
Adding @tjtanaa to review too.

[tjtanaa]

LGTM as well. RDNA also works.

[hongxiayang]

It can be merged as long as the CI passes.

[DarkLight1337]

Thanks for helping to review this!