[FEA]: write_to_vector_db module contains code specific to Milvus

[efajardo-nv]

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

Improvement

How would you describe the priority of this feature request

High

Please provide a clear description of problem this feature solves

The write_to_vector_db module contains a preprocess_vdb_resources function that uses pymilvus to create schema fields for creating a Milvus collection. This looks like it should instead be in milvus_vector_db_service.py.

Describe your ideal solution

Move code specific to a particular VDB to that VDB's service implementation.

Additional context

This is complicating Kinetica's development of their own Morpheus VDB service because they have their own API for creating collections.
Kinetica vector DB service feature request

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