Support cooldown to external lake table

[hoffermei]

Feature request

Is your feature request related to a problem? Please describe.

As data stored in olap table and the limit of local storage, we offten set a ttl(dynamic.start property) for local partition. When a partition reach it's ttl time, it will be delete by dynamic partition scheduler. If we config a table with big ttl, we must use more machine to store history data.

Another case is we sometimes need do offline analysis, expect to be independent with real time compute.

Describe the solution you'd like

Add a mechanism to cooldown olap table partition to external lake table, then history data could be save to lake table, offline analysis can be do on lake table with independent compute nodes.

Describe alternatives you've considered

Additional context

[hoffermei]

pr #45536

[LiShuMing]

After cooldown, what's the behavior of querying partitions (cooldown) ?