[Metax][CI] fix ci bugs

[plusNew001]

Motivation

💡 If this PR is a Cherry Pick, the PR title needs to follow the format by adding the [Cherry-Pick] label at the very beginning and appending the original PR ID at the end. For example, [Cherry-Pick][CI] Add check trigger and logic(#5191)

💡 如若此PR是Cherry Pick，PR标题需遵循格式，在最开始加上[Cherry-Pick]标签，以及最后面加上原PR ID，例如[Cherry-Pick][CI] Add check trigger and logic(#5191)

Modifications

Usage or Command

Accuracy Tests

Checklist

• Add at least a tag in the PR title.
  • Tag list: [[FDConfig],[APIServer],[Engine], [Scheduler], [PD Disaggregation], [Executor], [Graph Optimization], [Speculative Decoding], [RL], [Models], [Quantization], [Loader], [OP], [KVCache], [DataProcessor], [BugFix], [Docs], [CI], [Optimization], [Feature], [Benchmark], [Others], [XPU], [HPU], [GCU], [DCU], [Iluvatar], [Metax]]
  • You can add new tags based on the PR content, but the semantics must be clear.
• Format your code, run pre-commit before commit.
• Add unit tests. Please write the reason in this PR if no unit tests.
• Provide accuracy results.
• If the current PR is submitting to the release branch, make sure the PR has been submitted to the develop branch, then cherry-pick it to the release branch with the [Cherry-Pick] PR tag.

[paddle-bot]

Thanks for your contribution!

[plusNew001]

/skip-ci all

[Copilot]

Pull request overview

该 PR 聚焦于修复/稳定 Metax 相关 CI：调整 CI_METAX 工作流，避免在触发 Jenkins 任务前执行高风险/易失败的工作区清理操作，从而降低自托管 runner 上的 CI 失败概率。

Changes:

• 移除 .github/workflows/ci_metax.yml 中的 Cleanup 步骤（rm -rf * .[^.]*）。
• 保持其余流程不变：在自托管 XPU-P800 runner 上通过 MetaX-MACA/simple-jenkins-githubaction@v1.2 触发 Jenkins 的 paddle_fastdeploy_metax_smoketest 任务。

备注：PR 描述的 Motivation/Modifications/Usage/Tests 目前未填写，建议补充该变更要解决的具体 CI 报错现象与复现/验证方式，方便后续维护与回溯。

[PaddlePaddle-bot]

🤖 Paddle-CI-Agent | pr_review | 2026-05-26 17:28:12

📋 Review 摘要

PR 概述：移除 Metax CI workflow 中的 Cleanup 步骤以修复 CI 问题
变更范围：.github/workflows/ci_metax.yml
影响面 Tag：CI Metax

问题

级别	文件	概述
📝 PR 规范	PR 描述	Motivation 和 Modifications 章节内容为空，仅保留了 HTML 注释占位符

📝 PR 规范检查

PR 标题格式符合规范（含两个官方 Tag [Metax] 和 [CI]）。PR 描述中 ## Motivation 和 ## Modifications 章节内容为空（仅有 HTML 注释占位符），需补充实际内容。

标题建议（可直接复制）：

• [Metax][CI] fix ci bugs ✓ 已符合规范，无需修改

PR 描述建议（可直接复制，必须复刻 checklist §D2 模板的完整结构）：

## Motivation
移除 `.github/workflows/ci_metax.yml` 中过于激进的 Cleanup 步骤（`rm -rf * .[^.]*`），该步骤会在触发 Jenkins job 前删除工作目录下所有文件（含隐藏文件），可能导致 GitHub Actions runner 运行环境异常，从而引发 CI 失败。

## Modifications
- 删除 `.github/workflows/ci_metax.yml` 中的 `Cleanup` 步骤，该步骤执行 `rm -rf * .[^.]*` 清理工作目录

## Usage or Command
N/A

## Accuracy Tests
N/A

## Checklist

- [x] Add at least a tag in the PR title.
  - Tag list: [`[FDConfig]`,`[APIServer]`,`[Engine]`, `[Scheduler]`, `[PD Disaggregation]`, `[Executor]`, `[Graph Optimization]`, `[Speculative Decoding]`, `[RL]`, `[Models]`, `[Quantization]`, `[Loader]`, `[OP]`, `[KVCache]`, `[DataProcessor]`, `[BugFix]`, `[Docs]`, `[CI]`, `[Optimization]`, `[Feature]`, `[Benchmark]`, `[Others]`, `[XPU]`, `[HPU]`, `[GCU]`, `[DCU]`, `[Iluvatar]`, `[Metax]`]
  - You can add new tags based on the PR content, but the semantics must be clear.
- [x] Format your code, run `pre-commit` before commit.
- [x] Add unit tests. Please write the reason in this PR if no unit tests.
- [ ] Provide accuracy results.
- [ ] If the current PR is submitting to the `release` branch, make sure the PR has been submitted to the `develop` branch, then cherry-pick it to the `release` branch with the `[Cherry-Pick]` PR tag.

总体评价

变更内容简洁明确，删除有潜在风险的 Cleanup 步骤是合理的修复。建议补充 PR 描述中的 Motivation 和 Modifications 内容。