No Mark to Semi join conversion in statistics propagation

[Tmonster]

fixes #10950

Statistics propagation happens after unused columns are removed. We should not be changing projection maps at this time, and converting mark joins to semi joins effectively does this.

This logic is/was in #11573, but I am pulling it out because there are actually errors now in 0.10.2 that will be fixed with this. @lnkuiper, to address your question there about projection maps, we cannot just look at the projection map of the parent join. Suppose the mark -> semi join conversion happens on a child that is the right child of another join. Originally the right child was projecting N columns, and now it is projecting N-1 columns.

If some join further up in the plan has a right projection map and is expected something like N - X columns, now it will receive N - X - 1 columns, hence leading to these errors.

I'm open to different ways of implementing this logic. Was also think about some pre-optimizer step to inspect the projection maps beforehand to see what conversions are possible. This is difficult, however, as this knowledge will need to be communicated from the statistics propagator to the filter pushdown optimizer. May stew on this for a bit, but this is still a fix that should probably go in to v0.10.2.

[lnkuiper]

The fix looks good to me!

Since projection maps are a common source of pain, we might, at some point, want to look into changing them such that they use ColumnBindings during logical planning instead. I think this would solve a lot of logic errors. Maybe only when going to the physical plan do we use indices, just like when we go from BoundColumnRefExpression to BoundReferenceExpression.

Maybe the struct could look something like this:

struct ProjectionMapEntry {
    ColumnBinding binding; // Used during logical planning
    optional_idx index; // Used in the physical plan
};