[SL-1627] Add full support for predicate pushdown, including partition pruning

[tlento]

This is a large-scoped issue for all filter pushdown optimization requirements.

At a high level, we want to get a place where end users can specify filters in a way that is both natural and allows for easy hinting that filter predicates should be pushed down as far as they can go. This requires three things on the input interface side:

1. Allow users to split up predicates by semantic model in some natural way. This is done, actually, but we don't make use of it today. Users can, if they wish, provide a list of predicates which we will process as an intersection of filters (i.e., we will link them all with AND). For example, ["metric_time = '2021-01-01'", "user__country = 'CA' OR user__region = 'EMEA'"] is the same as metric_time = '2021-01-01' AND (user__country = 'CA' OR user__region = 'EMEA', but the former can have each statement pushed down to the constituent semantic models while the latter cannot (why not is a separate discussion, short version is we don't currently have the ability to do that level of semantic analysis).
2. Allow users to construct filters allowing us to properly apply range adjustments to time filters on metrics requiring expanded windows. For example, a cumulative metric with a 7-day aggregation window must include the week preceding the first date in the filter to return correct results for every requested output row.
3. Provide a way for users to ensure filters on partition columns are pushed down in such a manner that the underlying engine will trigger pruning.

Between our existing input interfaces and the addition of more robust partition specification options in the semantic manifest we should be able to provide all of these things. Indeed, we can deliver partial support for all of these scenarios without added updates to our input specifications. The sub-tasks listed here cover the major component pieces, and will be roughly addressed in the order in which they are created.

_SL-1627

Tasks

Beta Give feedback

1. [SL-1628] Update dataflow plan to push predicates down to semantic model source queries where possible #1011
   Metricflow +1
2. [SL-1629] Enable support for predicate pushdown for queries involving time range adjustments (e.g., offsets, cumulative) #1012
   Medium priority Metricflow +2
   
3. [SL-1630] Enable automatic time range adjustments for standard sets of time filter predicates #1013
   Low priority Metricflow +2
4. [SL-1631] Ensure predicate rendering is compatible with partition pruning directives across relevant engines #1014
   Medium priority Metricflow +2
   
5. [SL-1987] Post-join filter application on time spine queries results in invalid query exceptions #1119
   High priority Metricflow bug +3