[Bug]: When expiring historic data,the latest snapshot generated by amoro should not be used

[rfyu]

What happened?

For tables with the following configurations, data that should have been retained will be cleared after a long period of no ingestion, because the latest snapshot generated by data-expire operation is used when expiring historic data.

'data-expire.enabled' = 'true',
'data-expire.field' = 'd',
'data-expire.datetime-string-pattern' = 'yyyy-MM-dd',
'data-expire.retention-time' = '3d',
'data-expire.base-on-rule'='LAST_COMMIT_TIME'

Affects Versions

master

What engines are you seeing the problem on?

No response

How to reproduce

1. prepare an iceberg table and make sure the last commit is a week ago
2. add properties: 'data-expire.enabled' = 'true', 'data-expire.field' = 'd', 'data-expire.datetime-string-pattern' = 'yyyy-MM-dd', 'data-expire.retention-time' = '3d'
3. after the second data expiration, you will find that all data in this table has been cleared.

Relevant log output

No response

Anything else

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