[doc] fix: optimize ascend docs

[zheliuyu]

What does this PR do?

• 修复ascend_quick_start.rst中一些依赖软件的版本匹配错误。
• 支持现状表格中增加对actor.strategy和rollout.name的说明。
• 重命名ascend_profiling_en.rst和ascend_profiling_zh.rst，使文档标题看起来更美观些。

Checklist Before Starting

• Search for similar PRs. Paste at least one query link here: ...
• Format the PR title as [{modules}] {type}: {description} (This will be checked by the CI)
  • {modules} include fsdp, megatron, sglang, vllm, rollout, trainer, ci, training_utils, recipe, hardware, deployment, ray, worker, single_controller, misc, perf, model, algo, env, tool, ckpt, doc, data
  • If this PR involves multiple modules, separate them with , like [megatron, fsdp, doc]
  • {type} is in feat, fix, refactor, chore, test
  • If this PR breaks any API (CLI arguments, config, function signature, etc.), add [BREAKING] to the beginning of the title.
  • Example: [BREAKING][fsdp, megatron] feat: dynamic batching

Test

For changes that can not be tested by CI (e.g., algorithm implementation, new model support), validate by experiment(s) and show results like training curve plots, evaluation results, etc.

API and Usage Example

Demonstrate how the API changes if any, and provide usage example(s) if possible.

# Add code snippet or script demonstrating how to use this

Design & Code Changes

Demonstrate the high-level design if this PR is complex, and list the specific changes.

Checklist Before Submitting

Important

Please check all the following items before requesting a review, otherwise the reviewer might deprioritize this PR for review.

• Read the Contribute Guide.
• Apply pre-commit checks: pre-commit install && pre-commit run --all-files --show-diff-on-failure --color=always
• Add / Update the documentation.
• Add unit or end-to-end test(s) to the CI workflow to cover all the code. If not feasible, explain why: ...
• Once your PR is ready for CI, send a message in the ci-request channel in the verl Slack workspace. (If not accessible, please try the Feishu group (飞书群).)

[gemini-code-assist]

Code Review

本次PR主要优化了Ascend相关的文档，包括修复依赖版本错误、更新支持现状表格以及重命名文件以改善标题。

审查中发现 ascend_quick_start.rst 文件中存在两处内容不一致的问题：

1. transformers 库的版本号在文档内不同位置以及与 requirements-npu.txt 文件中的定义不一致。
2. 支持现状表格中 rollout.name 的值与快速入门示例及其他脚本中的配置不一致。

这些问题可能会导致用户在配置环境时产生困惑，建议进行修正以确保文档的准确性和一致性。其他更改看起来不错。