[Bug](runtime-filter) use rf_lock to lock local_state.conjuncts read operator

[BiteTheDDDDt]

What problem does this PR solve?

Currently, the reading and writing of conjuncts are not using the same lock, which may cause errors when reading conjuncts during vector expansion.

This pull request refactors how conjunct contexts are cloned in the scan operator pipeline. The main change is moving the responsibility for cloning conjunct contexts from the ScanLocalState class to the RuntimeFilterConsumerHelper class, simplifying the interface and improving encapsulation.

Refactoring and responsibility shift:

• Removed the clone_conjunct_ctxs method from ScanLocalState and its base class, along with related members such as _conjunct_lock. This simplifies the scan local state classes and reduces their responsibilities. [1] [2] [3] [4]
• Added a new clone_conjunct_ctxs method to RuntimeFilterConsumerHelper, which now handles cloning of conjunct contexts, including locking and context management. [1] [2]

Integration and usage updates:

• Updated the Scanner::try_append_late_arrival_runtime_filter method to use the new clone_conjunct_ctxs method from RuntimeFilterConsumerHelper instead of the previous approach.

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?

[BiteTheDDDDt]

run buildall

[BiteTheDDDDt]

run buildall

[github-actions]

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

[github-actions]

PR approved by anyone and no changes requested.

[HappenLee]

LGTM

[hello-stephen]

skip check_coverage