[FEA]: Switch to pymilvus >= 2.5

[dagardner-nv]

Is this a new feature, an improvement, or a change to existing functionality?

Change

How would you describe the priority of this feature request

Critical (currently preventing usage)

Please provide a clear description of problem this feature solves

Our current version of pymilvus is a bit out of date, and is needed to unblock NVIDIA/nv-ingest.

Describe your ideal solution

Switch to pymilvus 2.5

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct
• I have searched the open feature requests and have found no duplicates for this feature request

[dagardner-nv]

I looked into this a little bit and wanted to document what I ran into.
We are currently using the now deprecated milvus package which includes the milvus-server command allowing us to start a stand-alone local Milvus server. We use the milvus-server for testing and in our workflows which use Milvus.

The milvus package has since been replaced by the milvus-lite package, however it is not an exact 1:1 replacement and does not include the milvus-server command. Instead only allowing the client to connect directly to an on-disk db file.

Alternately we could use Milvus Standalone however the only supported operation for that is in Docker which would require a bit of work to get working in CI for tests.