[Improvement]: MaintainerMetrics Unified interface and Report

[czy006]

Search before asking

• I have searched in the issues and found no similar issues.

What would you like to be improved?

Currently, the maintainer has not yet perfected some metrics, and has only integrated the OrphanData-related indicators. We hope to expand the interfaces for other metrics.

How should we improve?

• MaintainerMetrics interface is abstracted to support a multi-lake architecture
• Maintainer Metrics add other maintainer metrics interface: such as expireSnapshots/expireData/cleanDanglingDeleteFiles/autoCreateTags
• MaintainerMetrics OrphanDataFiles method Change to a more general implementation

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Subtasks

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[baiyangtx]

It's a good idea.

I believe that for data lake formats, certain maintenance operations are universal: any snapshot-based management system will have snapshot expiration and orphan-file cleanup, and these operations can be designed as standardized metrics.

At present, Amoro focuses on the lake formats Paimon, Iceberg, and Lance; if a concept is identical across these three formats, it can be exposed uniformly at the AMS level.

[czy006]

It's a good idea.

I believe that for data lake formats, certain maintenance operations are universal: any snapshot-based management system will have snapshot expiration and orphan-file cleanup, and these operations can be designed as standardized metrics.

At present, Amoro focuses on the lake formats Paimon, Iceberg, and Lance; if a concept is identical across these three formats, it can be exposed uniformly at the AMS level.

After the design is completed, I will first showcase the interface solution here cc @baiyangtx @xxubai @zhoujinsong