[opt](recycler) Improve robustness and observability

[gavinchou]

What problem does this PR solve?

1. Fix delete non-existed object, the original impl. does not handle correctly
2. Add recycle lag indicators: bvars for index, partition, rowset and txn
   1. recycle_index_earlest_ts_${instance_id} dropped table/mv
   2. recycle_partition_earlest_ts_${instance_id} dropped partitions
   3. recycle_rowset_earlest_ts_${instance_id} compacted rowset
   4. recycle_tmp_rowset_earlest_ts_${instance_id} aborted transactions tmp data
   5. recycle_expired_txn_label_earlest_ts_${instance_id} expired labels and transactions
3. Add retry for scan_and_recycle() to prevent KV error like "Request future version"
4. Fix recycle delete instance may leak object data: we have to delete data first before delete KV
5. Improve code readability: remove duplicated code and add more comments

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

[hello-stephen]

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?

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[gavinchou]

run buildall

[qidaye]

run p1

[github-actions]

PR approved by anyone and no changes requested.

[hello-stephen]

run cloud_p1

[hello-stephen]

run p1

[gavinchou]

run buildall

[dataroaring]

LGTM

[github-actions]

PR approved by at least one committer and no changes requested.