[Bug]: Cgo Thread number go wild if delete hit large number of segments

[congqixia]

Is there an existing issue for this?

• [X] I have searched the existing issues

Environment

- Milvus version: 2.2.6
- Deployment mode(standalone or cluster): both
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

If a batch of delete operations hit a lot of segments, the thread number will go wild since each segment deletion happens in a dedicated goroutine

Expected Behavior

The thread number shall be controlled

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

Part of #23653