[NPU][Doc] Update GLM-5 docs, enabling deepep by default

[cen121212]

Motivation

When DeepEP is not enabled, there can be accuracy issues, so DeepEP is enabled by default.

Modifications

docs/platforms/ascend/ascend_npu_glm5_examples.md

Accuracy Tests

Speed Tests and Profiling

Checklist

• Format your code according to the Format code with pre-commit.
• Add unit tests according to the Run and add unit tests.
• Update documentation according to Write documentations.
• Provide accuracy and speed benchmark results according to Test the accuracy and Benchmark the speed.
• Follow the SGLang code style guidance.

Review and Merge Process

1. Ping Merge Oncalls to start the process. See the PR Merge Process.
2. Get approvals from CODEOWNERS and other reviewers.
3. Trigger CI tests with comments or contact authorized users to do so.
   • Common commands include /tag-and-rerun-ci, /tag-run-ci-label, /rerun-failed-ci
4. After green CI and required approvals, ask Merge Oncalls or people with Write permission to merge the PR.

[gemini-code-assist]

Code Review

This pull request updates the Ascend NPU GLM5 documentation by removing specific environment variables and increasing the maximum batch size for CUDA graphs. A review comment correctly identifies that the 'deepep' backend is incompatible with Ascend NPU hardware and suggests using 'ascend_fuseep' instead, while also recommending the removal of the 'deepep-mode' flag.

[gemini-code-assist]

For Ascend NPU, the optimized MoE All-to-All backend is ascend_fuseep. The deepep backend is specifically designed for NVIDIA GPUs using the deep_ep library and will not work on NPU. Additionally, --deepep-mode is not used by the ascend_fuseep backend and should be removed.

Suggested change

	--moe-a2a-backend deepep \
	--deepep-mode auto \
	--moe-a2a-backend ascend_fuseep \

[iforgetmyname]

/tag-and-rerun-ci

[zijiexia]

Hi @cen121212 , we've moved our documentations under docs_new so your changes here might not be correctly reflected on our documentation page. Can you kindly migrate this change to the corresponding page under docs_new? Thank you so much! sorry for any confusions.