CI: optimize unit test

[Song-Quan]

• Trigger unit tests based on the changed code
• Extract duplicate code as commands

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[Song-Quan]

I have read the CLA Document and I hereby sign the CLA

[gemini-code-assist]

The change from run_unittest to run_go_ut seems reasonable given the PR title 'CI: optimize unit test'. However, could you elaborate on why the other mappings (bazel, cmd, engine, pkg, .bazelrc, .circleci/unittest-config.yml) were removed? Are these tests now covered under the run_go_ut or are they being handled differently? Understanding the reasoning behind these removals will help ensure that the change doesn't inadvertently reduce test coverage.

[rivertalk]

@gemini-code-assist PTAL

[gemini-code-assist]

PTAL means 'Please Take A Look'. I will review the pull request now.

[FollyCoolly]

@gemini-code-assist explain this PR

[gemini-code-assist]

The PR aims to optimize the unit test process by triggering tests based on changed code and extracting duplicate code into reusable commands. I'll provide a summary of the changes below:

• .circleci/config.yml: Modified to differentiate between Go and C++ unit tests, triggering different workflows based on file changes.
• .circleci/unittest-config.yml: Substantial changes including:
  • Introduction of run_go_ut and run_cpp_ut parameters.
  • Definition of new commands: setup_cpp_test, run_go_test, and run_cpp_test to encapsulate test execution logic.
  • Refactoring of existing jobs (linux_scdb_ut, linux_engine_ut, macOS_scdb_ut, macOS_engine_ut) to use the new commands.
  • Addition of new jobs (linux_cpp_ut, macOS_cpp_ut) for C++ unit tests.
• Workflows: Updated to use run_go_ut and run_cpp_ut workflows, triggering the corresponding jobs based on the defined parameters.

[tongke6]

LGTM

[tongke6]

@jingshi-ant please take a final look

[jingshi-ant]

LGTM