[Cherry-pick](branch-2.1) Pick "[Enhancement](compaction) Do not set failure time when cumulative compaction dealing with delete rowset (#43466)"

[Yukang-Lian]

Before this PR, in cases where there is an alternating distribution of data rowset -> delete rowset -> data rowset -> delete rowset, cumulative compaction would only move the cumulative point forward to allow base compaction to handle the delete rowset. Cumulative compaction itself would not process the data and would return be marked as failure. This would cause the compaction submission task process to pause for 5 seconds, impacting efficiency.

This PR modifies the return status to OK for such cases, which improves the efficiency of the compaction submission task.

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Pick #43466

Problem Summary:

Release note

None

Check List (For Author)

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:
    • This is a refactor/code format and no logic has been changed.
    • Previous test can cover this change.
    • No code files have been changed.
    • Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.
  • Yes.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label

[Thearas]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?

[Yukang-Lian]

run buildall

[doris-robot]

TeamCity be ut coverage result:
Function Coverage: 36.39% (9540/26218)
Line Coverage: 27.90% (78603/281755)
Region Coverage: 26.57% (40354/151859)
Branch Coverage: 23.33% (20436/87610)
Coverage Report: http://coverage.selectdb-in.cc/coverage/d95effbbc587b25f7ba63b51b07e39062d6f24c5_d95effbbc587b25f7ba63b51b07e39062d6f24c5/report/index.html