Capture planner decisions to use a filtered index as a plan constraint

[hatyo]

When planning a query the planner might choose a filtered index if the query has compile-time predicates that are enclosed by the filtered index ranges. We should capture these condition(s) and model them as constraint(s) on the resulting execution plan.

By doing so, we can check, in plan cache, whether an optimised plan is feasible for a given logical plan given the logical plan's set of literals.