Bump vLLM version to v0.10.2rc3

[Yikun]

What this PR does / why we need it?

Bump vLLM version to v0.10.2rc3
vllm-project/vllm@v0.10.2rc2...v0.10.2rc3

Does this PR introduce any user-facing change?

No

How was this patch tested?

CI passed

• vLLM version: v0.10.2rc2
• vLLM main: vllm-project/vllm@15b8fef

[github-actions]

👋 Hi! Thank you for contributing to the vLLM Ascend project. The following points will speed up your PR merge:‌‌

• A PR should do only one thing, smaller PRs enable faster reviews.
• Every PR should include unit tests and end-to-end tests ‌to ensure it works and is not broken by other future PRs.
• Write the commit message by fulfilling the PR description to help reviewer and future developers understand.

If CI fails, you can run linting and testing checks locally according Contributing and Testing.

[gemini-code-assist]

Code Review

This pull request updates the vLLM version to v0.10.2rc3 and downgrades the CANN version to 8.2.rc1 across various Dockerfiles and documentation files. The changes are mostly consistent. However, I've pointed out an issue in docs/source/conf.py where several version variables used for documentation generation were not updated, which could lead to user confusion. Please address this to ensure the documentation is aligned with the code changes.

[gemini-code-assist]

While ci_vllm_version is correctly updated to v0.10.2rc3, several other version-related variables in the myst_substitutions dictionary are outdated. This will cause the installation documentation to point to older versions of vllm and vllm-ascend, which is inconsistent with the changes in this PR and will likely confuse users trying to build from source or install from pip.

Please update the related versions for consistency. For example:

    'vllm_version': 'v0.10.2rc3',
    'vllm_ascend_version': 'v0.10.2rc3', # Or the corresponding vllm-ascend tag for this change
    'pip_vllm_ascend_version': "0.10.2rc3", # Or the corresponding vllm-ascend tag for this change
    'pip_vllm_version': "0.10.2rc3",

This will ensure that the documentation for building from source and installing from pip reflects the new version.

[Yikun]

no, we shouldn't upgrade here