[AMORO-4208] Refactor orphan-files-cleaning via ProcessFactory plugin

[zhangwl9]

Why are the changes needed?

Close #4208.

Brief change log

Refactor Iceberg orphanFiles cleaning from the inline scheduler into a pluggable process model (ProcessFactory + ExecuteEngine) refer to #4107 :

Implementation Plan

1. Create OrphanFilesCleaningProcess

   • Implement TableProcess and LocalProcess interfaces
   • Add to IcebergProcessFactory with proper trigger strategy
   • Support configuration: clean-orphan-files.enabled and clean-orphan-files.interval

2. Remove standalone scheduler

   • Delete OrphanFilesCleaningExecutor from InlineTableExecutors
   • Remove registration from AmoroServiceContainer

3. Add configuration options

   • clean-orphan-files.enabled (default: true)
   • clean-orphan-files.interval (default: 1 day)
   • Configure via process-factories.yaml plugin config

4. Enhance state tracking

   • Use TableRuntimeCleanupState to track last orphan files clean time

5. Update execution engine config

   • Add pool.orphan-files-cleaning.thread-count to execute-engines.yaml

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)

[zhangwl9]

@czy006 @xxubai Could you please take a look at this PR in your spare time to see if it’s needed and if there are any issues with the code? If you find any problems, please let me know right away. Thank you very much.

[zhoujinsong]

The old global configs in AmoroManagementConf are still present after this refactor:

// AmoroManagementConf.java
public static final ConfigOption<Boolean> CLEAN_ORPHAN_FILES_ENABLED = ...
public static final ConfigOption<Integer> CLEAN_ORPHAN_FILES_THREAD_COUNT = ...
public static final ConfigOption<Duration> CLEAN_ORPHAN_FILES_INTERVAL = ...

And AmoroManagementConfValidator still validates them. Since the configuration has moved to process-factories.yaml, these entries are now dead code. They should either be removed or marked @Deprecated with a note pointing to the new config location, to avoid confusing users who upgrade and wonder why their old ams.yaml settings are silently ignored.