Migrate from MilvusClient to AsyncMilvusClient

[mattf]

🚀 Describe the new functionality needed

Update the current codebase to replace all instances of MilvusClient with AsyncMilvusClient. This migration should support all existing functionalities using asynchronous equivalents, ensuring compatibility with Milvus operations (e.g., collection management, data insertion, querying, indexing) in an async programming model.

The new implementation should:

• Use AsyncMilvusClient for all interactions with Milvus
• Support asynchronous workflows using async/await
• Maintain or improve current performance and stability
• Be backward-compatible where possible or provide migration guidelines

💡 Why is this needed? What if we don't build it?

Alignment with Milvus SDK and Future Roadmap: Milvus SDK v2 emphasizes async-first functionality and concurrent workflows Milvus SDK v2.

Other thoughts

No response

[Elbehery]

can i take this ?

[Elbehery]

cc @leseb

[mattf]

can i take this ?

go for it!

[Elbehery]

please assign me :)

[Elbehery]

❤️

[github-actions]

This issue has been automatically marked as stale because it has not had activity within 60 days. It will be automatically closed if no further activity occurs within 30 days.

[mattf]

milvus client has progressed with async support, e.g. milvus-io/pymilvus#2411. it's worth looking into this again.

cc @bbrowning @franciscojavierarceo

[Elbehery]

Thanks @mattf for your follow up

shall i re-open #2689 ?

[Elbehery]

@mattf i raised #3376 ptal 👍🏽