feat: Use writebuffer refactory With level zero delta policy

[XuanYang-cn]

In addition to the usage of refactory of datanode, This PR changes delta_policy to "l0_policy".

See also: #27675

[mergify]

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

[mergify]

@XuanYang-cn, 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]

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

[mergify]

@XuanYang-cn ut workflow job failed, comment rerun ut can trigger the job again.

[mergify]

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

[mergify]

@XuanYang-cn ut workflow job failed, comment rerun ut can trigger the job again.

[mergify]

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

[mergify]

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

[mergify]

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

[mergify]

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

[mergify]

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

[sre-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: XuanYang-cn
To complete the pull request process, please assign wxyucs after the PR has been reviewed.
You can assign the PR to them by writing /assign @wxyucs 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:

• configs/OWNERS
• internal/datanode/OWNERS
• pkg/util/OWNERS

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

[mergify]

@XuanYang-cn, 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]

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

[codecov]

Codecov Report

Merging #28336 (a0d643b) into master (cc71393) will decrease coverage by 0.02%.
Report is 4 commits behind head on master.
The diff coverage is 68.75%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #28336      +/-   ##
==========================================
- Coverage   81.79%   81.77%   -0.02%     
==========================================
  Files         833      842       +9     
  Lines      117654   117684      +30     
==========================================
+ Hits        96235    96237       +2     
- Misses      18188    18212      +24     
- Partials     3231     3235       +4     

Files	Coverage Δ
internal/datanode/metacache/segment.go	100.00% <100.00%> (ø)
internal/datanode/syncmgr/meta_writer.go	82.45% <100.00%> (+0.15%)	⬆️
internal/datanode/syncmgr/task.go	80.00% <ø> (-3.92%)	⬇️
internal/datanode/writebuffer/bf_write_buffer.go	85.36% <100.00%> (+0.36%)	⬆️
internal/datanode/writebuffer/sync_policy.go	91.66% <100.00%> (+0.49%)	⬆️
pkg/util/paramtable/component_param.go	98.20% <100.00%> (ø)
internal/datanode/writebuffer/write_buffer.go	88.51% <66.66%> (ø)
internal/datanode/syncmgr/options.go	95.52% <0.00%> (-4.48%)	⬇️
internal/datanode/metacache/actions.go	94.20% <0.00%> (-5.80%)	⬇️
internal/datanode/writebuffer/l0_write_buffer.go	72.30% <70.83%> (+4.12%)	⬆️

... and 166 files with indirect coverage changes

[mergify]

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

[mergify]

@XuanYang-cn

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.

[mergify]

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