[Feature]: Save the last completion time of the executor cleanup

[zhangwl9]

Description

The Amoro cleanup executor triggers its first execution when AMS starts, and subsequently runs periodically according to its respective interval.
The following scenario exists:
When the Amoro cleanup executor has just finished running a few minutes ago, the AMS service is manually restarted, causing the cleanup executor to run again.

Use case/motivation

Clearing executors should not be triggered frequently before and after ams service restart.

Describe the solution

After the AMS service restarts, whether the executor for optimizing tables cleans up immediately depends on whether the interval since the last completion time exceeds a fixed execution interval.

Subtasks

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

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