[Optimization]: 🔨 add thread-safe wrapper around rand.Shuffle and improve performance.

[yafengio]

This PR is aimed at enhancing performance and code maintainability while ensuring concurrent safety.

Here are the simple performance test results:

Benchmark_SafeRandShuffle/new_rand
Benchmark_SafeRandShuffle/new_rand-12         	   68043	     19829 ns/op	    5376 B/op	       1 allocs/op

Benchmark_SafeRandShuffle/safe_rand
Benchmark_SafeRandShuffle/safe_rand-12        	64563002	        16.04 ns/op	       0 B/op	       0 allocs/op

ref: #1314

cc @nirrozenbaum @ahg-g

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: yafengio
Once this PR has been reviewed and has the lgtm label, please assign terrytangyuan for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for gateway-api-inference-extension ready!

Name	Link
🔨 Latest commit	21e9283
🔍 Latest deploy log	https://app.netlify.com/projects/gateway-api-inference-extension/deploys/68971e8c2397a40008aaa99d
😎 Deploy Preview	https://deploy-preview-1335--gateway-api-inference-extension.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[k8s-ci-robot]

Hi @yafengio. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kfswain]

Have we validated the concurrency limits here? In scale testing, simply creating a new rand object performed fine. I wasn't sure how the lock contention would perform in high concurrency situations

[yafengio]

Have we validated the concurrency limits here? In scale testing, simply creating a new rand object performed fine. I wasn't sure how the lock contention would perform in high concurrency situations

Yes, I did a benchmark test. Compared with creating a new instance each time, the overhead of the lock is very small.

[yafengio]

Hi @kfswain , optimized with sync.Pool to reduce lock overhead and added benchmark tests. Please review. Thx