Supporting snapshot based time travel for Feast

[HaoXuAI]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

The current Feast use timestamp to support time travel. With the upcoming integration with Iceberg, deltalake etc, we need to support snapshots based time travel as well.

• How materialize can use snapshot to incrementally load data.
• How get_historical_features can use snapshot to get the features at that time point.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[HaoXuAI]

@franciscojavierarceo @jfw-ppi

[franciscojavierarceo]

FYI @ntkathole

[jfw-ppi]

With snapshot-based time travel, would we ensure that the response schema remains defined by the FeatureView and does not implicitly vary based on the store or snapshot? If a snapshot is schema-incompatible, should this fail explicitly rather than changing behavior per store?