[Enhancement] Improve CI efficiency by removing redundant mvn test step

[chi3316]

Before Creating the Enhancement Request

• I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

Currently, the mvn package phase already includes the test goal, leading to unnecessary repetition when mvn test is explicitly run again. This change aims to simplify the CI process andimproving overall efficiency.

Motivation

The project's unit tests are currently unstable, and running tests multiple times within a single CI job increases the likelihood of CI failures due to the inherent instability. By eliminating the redundant test step, we can reduce the risk of false negatives in CI results, saving developer time and resources.

Describe the Solution You'd Like

• Remove the explicit mvn test step from the CI workflow.
• Ensure that the existing mvn package step handles all necessary test executions.

Describe Alternatives You've Considered

Keeping the mvn test step with different configurations (e.g., different JVM options) to attempt to stabilize the tests. However, this approach could still lead to increased CI failures and does not address the root cause of test instability.

Additional Context

No response