[ci] chore: Rename dockerfile and update e2e_ascend

[FightingZhen]

What does this PR do?

1. Rename Ascend Dockerfile name for further evolution.
2. Update e2e_ascend CI docker image address to daily built docker image.
3. Some tiny optimize in e2e_ascend and Ascend Dockerfile.

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

Not related.

API and Usage Example

Not related.

Design & Code Changes

Not related.

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

This pull request renames a Dockerfile for Ascend, updates the corresponding documentation, and adds a command to list installed packages during the Docker build. The renaming and documentation updates are correct. However, the new command is added in a way that creates an unnecessary Docker image layer, which is inefficient. I've provided a high-severity comment with a suggestion to chain commands to optimize the image size, adhering to Docker best practices.