bump go to 1.22.3, fix make compose and optimize ut script

[guguducken]

User description

What type of PR is this?

• API-change
• BUG
• Improvement
• Documentation
• Feature
• Test and CI
• Code Refactoring

Which issue(s) this PR fixes:

issue # https://github.com/matrixorigin/MO-Cloud/issues/3413 https://github.com/matrixorigin/MO-Cloud/issues/3397

What this PR does / why we need it:

1. bump go version from 1.21.5 to 1.22.3
2. fix make compose to make it work
3. make ut will read UT_WORKDIR env variable to store report, it will be $HOME if UT_WORKDIR is empty

---

PR Type

Enhancement, Tests

---

Description

• Bumped Go version from 1.21.5 to 1.22.3 across multiple Dockerfiles and go.mod.
• Updated log export and Docker image handling in compose_bvt.sh.
• Improved database readiness check and updated test resource paths in entrypoint.sh.
• Changed default COMPOSE_LAUNCH value and added cleanup commands in Makefile.
• Removed version declaration from Docker Compose file.

---

Changes walkthrough 📝

	Relevant files
Enhancement	compose_bvt.sh Update log export and Docker image handling in compose_bvt.sh optools/compose_bvt/compose_bvt.sh Removed .bak file deletion in export_logs function. Updated file extensions for stack dump logs. Changed Docker image tag format in compose_bvt function. Removed redundant exit $? statement. +5/-8      entrypoint.sh Improve database readiness check and update test resource paths optools/compose_bvt/entrypoint.sh Modified database readiness check logic in run_bvt function. Updated paths for test resources in run_bvt function. +5/-3      Makefile Update compose launch configuration and cleanup commands  Makefile Changed default COMPOSE_LAUNCH value. Added forced removal of Docker volume in compose-clean. Added cleanup commands for test resources in compose-clean. +5/-2
Configuration changes	compose.yaml Remove version declaration from Docker Compose file            etc/launch-tae-compose/compose.yaml Removed version declaration from compose.yaml. +0/-2
Dependencies	go.mod Bump Go version to 1.22.3                                                                go.mod Bumped Go version from 1.21.5 to 1.22.3. +1/-1      Dockerfile Update base image to Go 1.22.3 in bvt_ut Dockerfile            optools/bvt_ut/Dockerfile Updated base image to use Go 1.22.3. +1/-1      Dockerfile.tester Update base image to Go 1.22.3 in Dockerfile.tester            optools/compose_bvt/Dockerfile.tester Updated base image to use Go 1.22.3. Removed installation of mariadb-client. +2/-3      Dockerfile Update base image to Go 1.22.3 in images Dockerfile            optools/images/Dockerfile Updated base image to use Go 1.22.3. +1/-1

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[codiumai-pr-agent-pro]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

PR Review 🔍

⏱️ Estimated effort to review [1-5]	3, because the PR involves multiple files and changes across scripts, Dockerfiles, and configuration files. The changes are moderate in complexity, involving updates to version numbers, script logic, and Docker configurations. Reviewing this PR requires understanding the impact of these changes on the build and deployment process, as well as ensuring that the updated scripts and Docker configurations function as expected.
🧪 Relevant tests	No
⚡ Possible issues	Possible Bug: The removal of the .bak file deletion in compose_bvt.sh might lead to accumulation of backup files if they are not managed elsewhere.
	Possible Bug: Changing the database readiness check in entrypoint.sh to only check for the presence of databases instead of specific tables might not be sufficient to ensure the database is fully ready for operations.
🔒 Security concerns	No

[codiumai-pr-agent-pro]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

PR Code Suggestions ✨

Category	Suggestion	Score
Possible issue	Add error handling for curl commands to log failures when fetching debug profiles Add error handling for the curl commands to ensure that any issues with fetching the debug profiles are caught and logged. optools/compose_bvt/compose_bvt.sh [10-11] -curl http://localhost:12345/debug/pprof/goroutine\?debug=2 -o docker-compose-log/cn-0-dump-stacks -curl http://localhost:22345/debug/pprof/goroutine\?debug=2 -o docker-compose-log/cn-1-dump-stacks +curl http://localhost:12345/debug/pprof/goroutine\?debug=2 -o docker-compose-log/cn-0-dump-stacks || echo "Failed to fetch debug profile from cn-0" +curl http://localhost:22345/debug/pprof/goroutine\?debug=2 -o docker-compose-log/cn-1-dump-stacks || echo "Failed to fetch debug profile from cn-1" Suggestion importance[1-10]: 7 Why: Adding error handling to the curl commands is a good practice to ensure robustness in case of network or server issues. The suggestion correctly identifies the new code and proposes a useful improvement.	7
Performance	Add a sleep interval inside the while true loop to prevent excessive CPU usage Add a sleep interval inside the while true loop to avoid a tight loop that could consume excessive CPU resources. optools/compose_bvt/entrypoint.sh [19-25] while true; do if mysql -h cn0 -P 6001 -u dump -p111 --execute "show databases;"; then break; fi if [ $i -ge 300 ]; then echo "wait for $i seconds, mo init not finish, so exit 1" docker ps + fi + sleep 1 + i=$(($i+1)) +done Suggestion importance[1-10]: 6 Why: The suggestion to add a sleep interval is valid and would help in reducing CPU usage. However, the suggested code already includes a sleep command and increment of the counter outside the if block, which makes this suggestion partially redundant.	6
Maintainability	Use a variable to store the common URL part for the curl commands to avoid repetition Use a variable to store the common URL part for the curl commands to avoid repetition and make future changes easier. optools/compose_bvt/compose_bvt.sh [10-11] -curl http://localhost:12345/debug/pprof/goroutine\?debug=2 -o docker-compose-log/cn-0-dump-stacks -curl http://localhost:22345/debug/pprof/goroutine\?debug=2 -o docker-compose-log/cn-1-dump-stacks +local base_url="http://localhost" +curl ${base_url}:12345/debug/pprof/goroutine\?debug=2 -o docker-compose-log/cn-0-dump-stacks +curl ${base_url}:22345/debug/pprof/goroutine\?debug=2 -o docker-compose-log/cn-1-dump-stacks Suggestion importance[1-10]: 6 Why: Using a variable for the common URL part is a good practice for maintainability. The suggestion correctly targets the new code and offers a clear improvement.	6
Best practice	Use $(RM) instead of rm -rf for removing directories and files for better portability Use $(RM) instead of rm -rf for removing directories and files to leverage the built-in make variable for better portability. Makefile [209-211] -@cd $(ROOT_DIR) && rm -rf docker-compose-log && rm -rf test/distributed/resources/json/export* -@cd $(ROOT_DIR) && rm -rf test/distributed/resources/into_outfile/*.csv -@cd $(ROOT_DIR) && rm -rf test/distributed/resources/into_outfile_2/*.csv +@cd $(ROOT_DIR) && $(RM) -rf docker-compose-log && $(RM) -rf test/distributed/resources/json/export* +@cd $(ROOT_DIR) && $(RM) -rf test/distributed/resources/into_outfile/*.csv +@cd $(ROOT_DIR) && $(RM) -rf test/distributed/resources/into_outfile_2/*.csv Suggestion importance[1-10]: 5 Why: The suggestion to use $(RM) instead of rm -rf is a good practice for portability in Makefiles. However, it's a minor improvement and not critical for functionality.	5