[Bug] E2E and benchmark deployment dependency causes task blocking

[chi3316]

Before Creating the Bug Report

• I found a bug, not just asking a question, which should be created in GitHub Discussions.

• I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

• I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

Github Action

RocketMQ version

branch: develop

JDK Version

No response

Describe the Bug

In the current GitHub Actions workflow, the e2e and benchmark cluster deployment tasks are running in parallel using matrix. However, if one of the cluster deployments (e.g., e2e) fails, it blocks the execution of the other cluster's tasks (e.g., benchmark), and vice versa. These tasks should be independent and not affect each other. If the e2e deployment fails, benchmark should continue and execute as normal; similarly, if benchmark deployment fails, e2e tests should still proceed.

Steps to Reproduce

1. Configure GitHub Actions to run e2e and benchmark cluster deployments in parallel using matrix.
2. Ensure that the e2e cluster deployment fails while the benchmark deployment succeeds.
3. Notice that the benchmark tasks do not proceed as expected and are blocked.

What Did You Expect to See?

Even if the e2e cluster deployment fails, the benchmark should continue to execute and complete its tasks successfully.

What Did You See Instead?

After the e2e cluster deployment fails, the benchmark tasks do not continue and are blocked.

Additional Context

No response