Switch to using testcontainers in the tests

[roji]

Our tests currently rely on an externally available Milvus instance. This makes it a bit harder to contribute, and also complicates our CI.

We can instead use testcontainers.net; note that there already are testcontainer modules for Milvus, but currently only for

[weianweigan]

@roji It's cool! I am new to Testcontainers. I searched for modules on testcontainers.net and found that Milvus in Testcontainers seems to only support Java and Go. However, I noticed that #58 is using it. Is it also available for .NET?

Does this imply that we can conveniently test multiple versions of Milvus simultaneously?"

[roji]

Is it also available for .NET?

Unfortunately not - as you've found out, testcontainers modules currently exist only for Java and Go.

However, in #58 I implemented such a module, and the plan is to submit that to be a part of testcontainers alongside the existing Java/Go ones. This would enable .NET developers to easily test against Milvus.

[roji]

Does this imply that we can conveniently test multiple versions of Milvus simultaneously?

Yeah, this will simplify that. However, I took a look at 2.2, and that version is quite difficult to get running properly (2.3 is much simpler). I think we probably may want to just concentrate on 2.3 going forward - people still targeting 2.2 can use the 2.2 version of the SDK in any case. But future versions can indeed be tested as a test matrix in Github Actions in a pretty easy way using testcontainers.