Consider filter condition of index access path in skyline pruning

## Enhancement
In current skylinePruning, we don't consider `AccessPath.IndexFilters`. This would results in nonoptimal plan sometimes.
For example, between (1) an index full scan + selection on the index + index lookup and (2) an table full scan + selection, without required order property, current logic would think (2) is better. But in some scenarios this is incorrect.