chore: remove a warn! introduced by mistake when debugging

[xxchan]

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.

What's changed and what's your intention?

as title

Checklist

Refer to a related PR or issue link (optional)

[codecov]

Codecov Report

Merging #3520 (9abb9b7) into main (9ab8ad2) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3520   +/-   ##
=======================================
  Coverage   74.46%   74.47%           
=======================================
  Files         769      769           
  Lines      108054   108052    -2     
=======================================
+ Hits        80462    80468    +6     
+ Misses      27592    27584    -8     

Flag	Coverage Δ
rust	74.47% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/batch/src/executor/row_seq_scan.rs	17.56% <ø> (+0.23%)	⬆️
src/frontend/src/expr/utils.rs	98.99% <0.00%> (+0.25%)	⬆️
src/connector/src/filesystem/file_common.rs	80.80% <0.00%> (+0.44%)	⬆️
src/meta/src/hummock/compaction_group/manager.rs	90.95% <0.00%> (+0.47%)	⬆️
src/meta/src/manager/id.rs	96.62% <0.00%> (+1.12%)	⬆️

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

[mergify]

Hey @xxchan, this pull request failed to merge and has been dequeued from the merge train. If you believe your PR failed in the merge train because of a flaky test, requeue it by commenting with @mergifyio requeue. More details can be found on the Queue: Embarked in merge train check-run.

[xxchan]

@Mergifyio requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically