Fix recursive outer nested loop join state reuse - #24700

A recursive CTE containing a FULL or RIGHT outer nested loop join could fail when the recursive executor reused its local source state. Assertion builds failed while initializing an already initialized scan chunk, while release builds could retain duplicate vectors and eventually access them out of bounds.

The local source reset path was calling OuterJoinMarker::InitializeScan on every recursive iteration. That function performs one-time initialization of the scan chunk, so calling it again violated the chunk lifecycle.

I moved that initialization into the nested loop join local scan state constructor. Reusing the state now resets the existing chunk and replaces its scan bookkeeping without reconstructing its schema or vector cache. This preserves recursive state reuse while giving each iteration a clean outer-join scan.

Fixes duckdb/duckdb-fuzzer#4635.

Fixes https://github.com/duckdblabs/duckdb-internal/issues/9824.