feat: Support multiple vector indexes in a collection

[xige-16]

issue: #25639

/kind improvement
Signed-off-by: xige-16 xi.ge@zilliz.com

[mergify]

@xige-16 E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

[mergify]

@xige-16 ut workflow job failed, comment rerun ut can trigger the job again.

[codecov]

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (b251c3a) 80.82% compared to head (249a7f2) 80.84%.
Report is 18 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #27700      +/-   ##
==========================================
+ Coverage   80.82%   80.84%   +0.01%     
==========================================
  Files         917      917              
  Lines      127051   126905     -146     
==========================================
- Hits       102689   102590      -99     
+ Misses      21033    20999      -34     
+ Partials     3329     3316      -13     

Files	Coverage Δ
internal/datacoord/index_service.go	94.74% <100.00%> (-0.03%)	⬇️
internal/datacoord/util.go	99.27% <100.00%> (+0.01%)	⬆️
internal/datacoord/index_meta.go	98.41% <97.50%> (-0.35%)	⬇️

... and 22 files with indirect coverage changes

[mergify]

@xige-16 E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

[mergify]

@xige-16 ut workflow job failed, comment rerun ut can trigger the job again.

[mergify]

@xige-16 E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

[mergify]

@xige-16, please be sure the pr should only have one commit, check https://github.com/milvus-io/milvus/blob/master/CODE_REVIEW.md for more details.

[mergify]

@xige-16 E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

[xige-16]

/run-cpu-e2e

[mergify]

@xige-16 E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

[mergify]

@xige-16 E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

[xige-16]

rerun ut

[mergify]

@xige-16

Invalid PR Title Format Detected

Your PR submission does not adhere to our required standards. To ensure clarity and consistency, please meet the following criteria:

1. Title Format: The PR title must begin with one of these prefixes:

• feat: for introducing a new feature.
• enhance: for improvements to existing functionality.
• fix: for bug fixes.

2. Description Requirement: The PR must include a non-empty description, detailing the changes and their impact.

Required Title Structure:

[Type]: [Description of the PR]

Where Type is one of feat, enhance, or fix.

Example:

feat: Enhance search functionality within the user interface

Please review and update your PR to comply with these guidelines.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

[mergify]

@xige-16 ut workflow job failed, comment rerun ut can trigger the job again.

[mergify]

@xige-16 ut workflow job failed, comment rerun ut can trigger the job again.

[mergify]

@xige-16 E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

[mergify]

@xige-16 E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

[xige-16]

/run-cpu-e2e

[xiaocai2333]

/lgtm

[czs007]

/approve

[sre-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: czs007, xige-16

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• internal/datacoord/OWNERS [czs007]
• internal/proto/OWNERS [czs007]
• internal/proxy/OWNERS [czs007]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment