Provide Qdrant Client Support and direct Aspire support for all 3rd parties and tooling including KM itself

[JohnGalt1717]

Contrary to the previous discussion this isn't resolved but was closed. The connection string from the proper Aspire.Hosting.Qdrant integration does not include the legacy REST connection endpoint, only the GRPC endpoint. Thus, it cannot be used because KM doesn't support GRPC communication for Qdrant because of the legacy implementation. Thus the claim made in the closing comment is both untrue

There are others that also have major problems with Aspire in addition to Qdrant.

Given that Aspire is one of the defining reasons for a major uptick in adoption for C# it's vital that this has support throughout KM and SK.

To that end, while I understand the legacy 3 year thing, it's vital that Qdrant be updated to accept a QdrantClient and to use qdrant client.

The same should be true for OllamaClient, OpenAiClient, Anthropic Client and KM should support the Microsoft.Extensions.AI abstractions as well for all of this.

Any other 3rd party integrations that have the same problem as Qdrant should be updated or added to to support their native clients and native Aspire functionality as a result.

It is not a solution to use docker support in Aspire to hack backwards compatibility with the legacy clients in KM especially since KM is still a beta product that hasn't even hit 1.0. If there is an Aspire implementation, KM and SK should be committed to supporting them directly along with Microsoft.Extensions.AI.

Further, KM should have its own Aspire implementation for using it in a docker container with remoting.

This should be a very high priority for Microsoft given it's AI push and the huge success of Aspire.