[CI] Fix path error of /re-run

[EmmonsCurse]

Motivation

Fix path error of /re-run to improve the developer experience when handling flaky tests or temporary CI issues.

Modifications

path

Usage or Command

To re-run CI jobs, comment the following under your Pull Request:

/re-run all-failed              # all-failed
/re-run approval                # Approval
/re-run ci_iluvatar             # CI_ILUVATAR
/re-run ci_xpu                  # CI_XPU
/re-run codestyle               # Pre Commit(alias: /re-run pre_commit)
/re-run clone                   # FD-Clone-Linux / code-clone
/re-run build                   # FD-Build-Linux / fd-build
/re-run run_ce_cases            # Extracted partial CE model tasks to run in CI. / run_ce_cases
/re-run accuracy_tests          # Run Accuracy Tests / accuracy_tests
/re-run base_tests              # Run Base Tests / base_tests
/re-run run_tests_logprob       # Run FastDeploy LogProb Tests / run_tests_logprob
/re-run run_tests_with_coverage # Run FastDeploy Unit Tests and Coverage / run_tests_with_coverage
/re-run diff_coverage_report    # Run FastDeploy Unit Tests and Coverage / diff_coverage_report
/re-run stable_tests            # Run Stable Tests / stable_tests

Accuracy Tests

This PR only modifies GitHub workflow logic and does not affect model accuracy or inference results.

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!