test(path): Optimize unit test execution results

[flc1125]

I found an official example, I see the official example for the number of CPU cores for comparison, so I made a reference to the official adjustment.

References:

• https://github.com/golang/go/blob/master/src/path/path_test.go#L82-L85
• testing: why AllocsPerRun tests fails when GOMAXPROCS>1 golang/go#5000
• https://codereview.appspot.com/7545043

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.18%. Comparing base (3dc1cd6) to head (a136e90).
Report is 24 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3883      +/-   ##
==========================================
- Coverage   99.21%   99.18%   -0.03%     
==========================================
  Files          42       43       +1     
  Lines        3182     2701     -481     
==========================================
- Hits         3157     2679     -478     
+ Misses         17       12       -5     
- Partials        8       10       +2     

Flag	Coverage Δ
	?
-race	∅ <ø> (?)
-tags "sonic avx"	99.17% <ø> (?)
-tags go_json	99.17% <ø> (?)
-tags nomsgpack	99.17% <ø> (?)
go-1.18	99.11% <ø> (-0.01%)	⬇️
go-1.19	99.18% <ø> (-0.03%)	⬇️
go-1.20	99.18% <ø> (-0.03%)	⬇️
go-1.21	99.18% <ø> (-0.03%)	⬇️
go-1.22	99.18% <ø> (?)
macos-latest	99.18% <ø> (-0.03%)	⬇️
ubuntu-latest	99.18% <ø> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[flc1125]

@appleboy As a complement to this: #3878 (comment)

[appleboy]

@flc1125 Thanks.