Track Issue: Optimize the execution time of go test cases

### Search before asking

- [x] I had searched in the [issues](https://github.com/apache/kvrocks/issues) and found no similar issues.

### Motivation

In current GitHub Action workflows, go test execution now often takes more than 30 minutes, which may affect our responsiveness and PR processing efficiency.

We need to analyze which test cases take too long and optimize their execution time without affecting the test results.

This PR is track for：
- #2642

Include:
- #3507
- #3526
- #3527
- #3528
- #3529
### Solution

_No response_

### Are you willing to submit a PR?

- [x] I'm willing to submit a PR!

Start by reviewing the current GitHub Actions workflows and the Go test cases to identify which tests exceed the execution target. Use tracked issues #3507, #3526, #3527, #3528, and #3529 as entry points, and consider the work done when test execution is faster without changing results.

Written by the indexing model from the issue text.