Remove Milvus.Client dependency.

[mitchdenny]

Description

Removing Milvus client dependency (incl health check) so we can ship the hosting package as GA.

Fixes #6431

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No (removed a unit test)
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue:
  • No

Microsoft Reviewers: Open in CodeFlow

[mitchdenny]

/backport to release/9.0

[github-actions]

Started backporting to release/9.0: https://github.com/dotnet/aspire/actions/runs/11469724726

[mitchdenny]

/backport to release/9.0

[github-actions]

Started backporting to release/9.0: https://github.com/dotnet/aspire/actions/runs/11470499191

[github-actions]

@mitchdenny backporting to release/9.0 failed, the patch most likely resulted in conflicts:

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Applying: Remove Milvus.Client dependency.
Applying: namespaces!
Using index info to reconstruct a base tree...
M	src/Aspire.Hosting.Milvus/MilvusBuilderExtensions.cs
M	src/Aspire.Hosting.Redis/RedisBuilderExtensions.cs
Falling back to patching base and 3-way merge...
Auto-merging src/Aspire.Hosting.Redis/RedisBuilderExtensions.cs
CONFLICT (content): Merge conflict in src/Aspire.Hosting.Redis/RedisBuilderExtensions.cs
Auto-merging src/Aspire.Hosting.Milvus/MilvusBuilderExtensions.cs
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0002 namespaces!
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

[github-actions]

@mitchdenny an error occurred while backporting to release/9.0, please check the run log for details!

Error: git am failed, most likely due to a merge conflict.

[eerhardt]

I think this is the right change for now. Hopefully Milvus.Client releases stable soon.

[mitchdenny]

/backport to release/9.0

[github-actions]

Started backporting to release/9.0: https://github.com/dotnet/aspire/actions/runs/11476514204

[github-actions]

@mitchdenny backporting to release/9.0 failed, the patch most likely resulted in conflicts:

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Applying: Remove Milvus.Client dependency.
Applying: namespaces!
error: sha1 information is lacking or useless (src/Aspire.Hosting.Milvus/MilvusBuilderExtensions.cs).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0002 namespaces!
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

[github-actions]

@mitchdenny an error occurred while backporting to release/9.0, please check the run log for details!

Error: git am failed, most likely due to a merge conflict.

[Alirexaa]

We should log an issue for Adding the health check to Milvus.