fix: fix miss makezero bug

[alingse]

I was running github actions to run linter makezero for top github golang repos.

see issues alingse/go-linter-runner#1

and the github actions output https://github.com/alingse/go-linter-runner/actions/runs/9241746915/job/25423640197

====================================================================================================
append to slice `partitionIDs` with non-zero initialized length at https://github.com/milvus-io/milvus/blob/master/internal/rootcoord/broker.go#L242:18
append to slice `pairs` with non-zero initialized length at https://github.com/milvus-io/milvus/blob/master/cmd/tools/migration/meta/2[10](https://github.com/alingse/go-linter-runner/actions/runs/9241746915/job/25423640197#step:4:11)_to_220.go#L64:11
append to slice `servers` with non-zero initialized length at https://github.com/milvus-io/milvus/blob/master/tests/integration/minicluster_v2.go#L257:13
====================================================================================================
Report issue: https://github.com/milvus-io/milvus/issues

[sre-ci-robot]

Welcome @alingse! It looks like this is your first PR to milvus-io/milvus 🎉

[sre-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: alingse
To complete the pull request process, please assign xiaofan-luan after the PR has been reviewed.
You can assign the PR to them by writing /assign @xiaofan-luan in a comment when ready.

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

Needs approval from an approver in each of these files:

• cmd/OWNERS
• internal/rootcoord/OWNERS
• tests/integration/OWNERS

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

[mergify]

@alingse Thanks for your contribution. Please submit with DCO, see the contributing guide https://github.com/milvus-io/milvus/blob/master/CONTRIBUTING.md#developer-certificate-of-origin-dco.

[mergify]

@alingse

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.
• fix: for bug fixes.
• enhance: for improvements to existing functionality.
• test: for add tests to existing functionality.
• doc: for modifying documentation.
• auto: for the pull request from bot.

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, fix, enhance, test or doc.

Example:

enhance: improve search performance significantly 

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

[mergify]

@alingse Please associate the related issue to the body of your Pull Request. (eg. “issue: #”)

[mergify]

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.17%. Comparing base (36cbce4) to head (88f3ff0).
Report is 529 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #33386      +/-   ##
==========================================
+ Coverage   82.12%   82.17%   +0.04%     
==========================================
  Files        1012     1012              
  Lines      128862   128862              
==========================================
+ Hits       105828   105892      +64     
+ Misses      19061    18997      -64     
  Partials     3973     3973              

Files	Coverage Δ
internal/rootcoord/broker.go	92.10% <100.00%> (ø)
tests/integration/minicluster_v2.go	72.72% <100.00%> (ø)

... and 38 files with indirect coverage changes

[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.

[alingse]

/reopen

[sre-ci-robot]

@alingse: Reopened this PR.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alingse]

/run-cpu-e2e

[mergify]

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

[alingse]

/assign @xiaofan-luan

[mergify]

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

[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.