[AMORO-3317]: Move optimizing planer and scan to iceberg/mixed-format module

[baiyangtx]

Why are the changes needed?

close #3317

Currently, the Optimizing Plan has become a bottleneck of AMS. A feasible solution is to delegate the Optimizing Plan to the Optimizer for execution.

For this, some prerequisite refactoring work is required.

This PR moves the code of the Optimizing Plan from the AMS module to the iceberg/mixed-format module, and the relevant logic can be called by the optimizer in the future.

Brief change log

• Move Optimizing Plan related codes to iceberg/mixed-format module
• Add a mixed-iceberg rewrite executor factory

How was this patch tested?

• [ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

• [ ] Add screenshots for manual tests if appropriate

• [ ] Run test locally before making a pull request

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

[baiyangtx]

LGTM. Question: After this refactoring, can Spark customize procedures to trigger optimization? （only depend on the plan and scan logical)

1. Committer still in ams-module
2. These refactorings only involve core-level code, and the engine still needs to adapt.