Extend OH SQL for snapshots retention

[teamurko]

Summary

Support configurable snapshots retention (SQL, PR1)

• time-based retention, supported hour and day granularity
• count-based retention, the most recent N are preserved when expiring snapshots

Next:

• Handle snapshotsRetention property
• Propagate the policy to ES app

Changes

• Client-facing API Changes
• Internal API Changes
• Bug Fixes
• New Features
• Performance Improvements
• Code Style
• Refactoring
• Documentation
• Tests

For all the boxes checked, please include additional details of the changes made in this pull request.

Testing Done

• Manually Tested on local docker setup. Please include commands ran, and their output.
• Added new tests for the changes made.
• Updated existing tests to reflect the changes made.
• No tests added or updated. Please explain why. If unsure, please feel free to ask for help.
• Some other form of testing like staging or soak time in production. Please explain.

For all the boxes checked, include a detailed description of the testing done for the changes made in this pull request.

Additional Information

• Breaking Changes
• Deprecations
• Large PR broken into smaller PRs, and PR plan linked in the description.

For all the boxes checked, include additional details of the changes made in this pull request.

[autumnust]

• shall we use something more simple like version instead of snapshots, the latter was a overloaded term that can also be used to describe a non-partitioned table.
• alternatively what about SET POLICY RETAIN 100 HOURS SET POLICY RETAIN 50 VERSIONS

[autumnust]

I know delta lake has something called VACCUM being similar. Maybe we can get some inspiration from Polaris for this syntax.