perf(s3stream): optimize StreamRecordBatchList to reduce object creation

[lifepuzzlefun]

1. remove ArrayList copy when create instance.
2. StreamRecordBatch will implement the ComparableItem interface without create wrap object.

[CLAassistant]

All committers have signed the CLA.

[daniel-y]

Hi @lifepuzzlefun thanks for your contribution. And, please check the failed actions.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (5cbd19c) 55.90% compared to head (67b1d08) 55.91%.

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #903      +/-   ##
============================================
+ Coverage     55.90%   55.91%   +0.01%     
- Complexity     1264     1266       +2     
============================================
  Files           133      133              
  Lines          8534     8534              
  Branches        789      789              
============================================
+ Hits           4771     4772       +1     
  Misses         3327     3327              
+ Partials        436      435       -1     

Components	Coverage Δ
RocketMQ Broker	∅ <ø> (∅)
RocketMQ Common	5.80% <ø> (ø)
RocketMQ Controller	57.39% <ø> (ø)
RocketMQ Proxy	37.28% <ø> (+0.10%)	⬆️
RocketMQ Store	73.56% <ø> (-0.05%)	⬇️
RocketMQ Stream	∅ <ø> (∅)
RocketMQ Metadata	35.44% <ø> (ø)

see 2 files with indirect coverage changes

[SCNieh]

LGTM, @lifepuzzlefun the commit msg lint seems failed, maybe rebase & rewrite the commit msg to something like: perf(s3stream): optimize StreamRecordBatchList

• xxx
• xxx

[Chillax-0v0]

@lifepuzzlefun You can use git rebase to modify commit messages:

1. Run this command in your branch "lifepuzzlefun:optimzie_stream_record_batch_list"

git rebase --interactive e5e20802771fe93c9fc72c46597b35a960db9712^

(e5e2080 is the first commit hash in your branch, and a '^' means the commit before the specified commit)
2. In the opened file, modify "pick"s to "reword"s. Then save and quit.
3. Then you will be able to modify each commit message.
4. After all, you can run git push --force to update commits in this branch, and actions in this PR will re-run automatically.

[lifepuzzlefun]

@SCNieh @Chillax-0v0 thanks for help. the commit message has been modified, hope the CI can pass. by the way, I think we need update the contribute guide to tell the contributors write commit message in the expected format.

[zhouxinyu]

We will merge the PR in a squash manner, so we don't need to modify the commit message one by one, just squashing all the commits to one commit is enough.

Anyway, I will remove the Lint Commit Messages action, since we don't need it anymore, sorry for your time. @lifepuzzlefun