[Doc][P/D] Fix MooncakeConnector's name (#5172)

### What this PR does / why we need it?
vLLM community has integrated their MooncakeConnector. The original
scripts will now find this MooncakeConnector instead of the one from
vLLM-Ascend. All scripts that involve using the MooncakeConnector need
to be modified to another name.

### Does this PR introduce _any_ user-facing change?
Yes, users need to use a new name to load vLLM-Ascend MooncakeConnector.

### How was this patch tested?
By CI.

- vLLM version: v0.12.0
- vLLM main:
ad32e3e19c

---------

Signed-off-by: nwpu-zxr <zhouxuerong2@huawei.com>

tests/e2e/nightly/multi_node/config/models/Qwen3-235B-W8A8-EPLB.yaml

@@ -33,7 +33,7 @@ deployment:
         --no-enable-prefix-caching
         --gpu-memory-utilization 0.9
         --kv-transfer-config
-        '{"kv_connector": "MooncakeConnector",
+        '{"kv_connector": "MooncakeConnectorV1",
         "kv_role": "kv_producer",
         "kv_port": "30000",
         "engine_id": "0",
@@ -70,7 +70,7 @@ deployment:
         --no-enable-prefix-caching
         --gpu-memory-utilization 0.9
         --kv-transfer-config
-        '{"kv_connector": "MooncakeConnector",
+        '{"kv_connector": "MooncakeConnectorV1",
         "kv_role": "kv_consumer",
         "kv_port": "30200",
         "engine_id": "1",