[Bug] CI Pipeline Failure in Golang E2E Tests

[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

5.2.0

JDK Version

No response

Describe the Bug

The CI pipeline for the Go e2e tests in the RocketMQ GitHub repository is failing due to an issue with the run.sh script. Specifically, the script attempts to source the env.sh file using source but encounters an error indicating that the file cannot be found. As a result, the script fails to execute properly, leading to the CI pipeline failure with an exit code of 2.

Steps to Reproduce

1. Trigger the CI pipeline in the GitHub Actions workflow.
2. Observe the failure in the Test E2E golang test stage.
3. Checking the logs, you can see that the exit code for the container is 2
   

What Did You Expect to See?

Test E2E golang where the container exit status code is 0 and the pipeline passes normally

What Did You See Instead?

The Test E2E golang cannot be executed, causing the CI pipeline to fail.

Additional Context

No response

[chi3316]

Summary of the Issue
I discovered that the primary cause of the Go e2e test failures was due to the use of an outdated Go version. The test environment was using Go 1.19, while some dependencies required Go 1.20 or higher. This version mismatch led to compatibility issues during the build and test processes.

Steps Taken to Resolve

1. Updated the Go version in the test environment image to 1.22.
2. Re-run the e2e test with the required configuration to ensure that the test scripts were executed correctly.
   The test workflow