[CI] Integrate mooncake to vllm-ascend base image

[Potabk]

What this PR does / why we need it?

This patch aims to integrate the mooncake v0.3.7.2.post2 to vllm-ascend images

Does this PR introduce any user-facing change?

How was this patch tested?

Test is locally:

docker build -t vllm-ascend-with-mooncake -f Dockerfile.a3 --network host .

Start the container after build is complete:

IMAGE=vllm-ascend-with-mooncake
docker run --rm \
--name test_nightly \
--device /dev/davinci2 \
--device /dev/davinci_manager \
--device /dev/devmm_svm \
--device /dev/hisi_hdc \
-v /usr/local/dcmi:/usr/local/dcmi \
-v /usr/local/Ascend/driver/tools/hccn_tool:/usr/local/Ascend/driver/tools/hccn_tool \
-v /usr/local/bin/npu-smi:/usr/local/bin/npu-smi \
-v /usr/local/Ascend/driver/lib64/:/usr/local/Ascend/driver/lib64/ \
-v /usr/local/Ascend/driver/version.info:/usr/local/Ascend/driver/version.info \
-v /etc/ascend_install.info:/etc/ascend_install.info \
-v /root/.cache:/root/.cache \
-it $IMAGE bash

test mooncake:

>>> from mooncake.engine import TransferEngine
>>> import mooncake

• vLLM version: v0.11.0
• vLLM main: vllm-project/vllm@83f478b

[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 integrates Mooncake into the vllm-ascend base images by updating several Dockerfiles and adding a new installer script. While the goal is clear, the implementation introduces several inefficiencies in the Docker build process and a few critical bugs in the new installer script. My review focuses on optimizing the Dockerfiles for smaller image size and faster builds by consolidating package installation steps, and on fixing critical issues in the installer script related to incorrect directory handling, flawed error checking, and ineffective environment variable management.