feat: estimate cardinality for semi and anti-joins using distinct counts (#20904)

## Which issue does this PR close?
Does not close but part of
#20766


## Rationale for this change
Details are in #20766. But main idea is to use existing distinct count
information to optimize joins similar to how Spark/Trino does

## What changes are included in this PR?
This PR extends cardinality estimation for semi/anti joins using
distinct counts

## Are these changes tested?
I've added cases but not sure if I should've added benchmarks on this. 

## Are there any user-facing changes?
No

---------

Co-authored-by: Alessandro Solimando <alessandro.solimando@gmail.com>

Author: buraksenn