[Improvement]: Refactor Optimizing Interface Move to amoro-common

### Search before asking

- [x] I have searched in the [issues](https://github.com/apache/amoro/issues?q=is%3Aissue) and found no similar issues.

### What would you like to be improved?

Refactor Optimizing Interface Move to amoro-common, Prepare abstract interfaces for optimized support of multi-lake formats.

### How should we improve?

- refactor: extract getStructLikeCollections from TaskProperties to AbstractRewriteFilesExecutor
- refactor: move optimizing SPI interfaces from amoro-format-iceberg to amoro-common
- refactor: replace Iceberg DynConstructors with amoro-common DynConstructors in OptimizerExecutor

### Are you willing to submit PR?

- [x] Yes I am willing to submit a PR!

### Subtasks

_No response_

### Code of Conduct

- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

Start by tracing TaskProperties.getStructLikeCollections, AbstractRewriteFilesExecutor, and OptimizerExecutor, then locate the optimizing SPI interfaces in the repository. Confirm the existing Iceberg DynConstructors usage and the amoro-common equivalents before changing ownership. Done means the interfaces and constructor usage are moved consistently and the optimizer continues to support the targeted multi-lake formats.

Written by the indexing model from the issue text.