Dataflow Gen2: auto mapping doesn't re-evaluate parameterized destination table columns at runtime

Using a parameter for the destination table appears supported, but it isn't — unless the destination table's columns are identical to what was set during the preview at publish time.

The source query re-evaluates per run, but the auto destination mapping stays locked to the published preview schema. So if the parameterized table has different columns, the refresh fails:

The column '<name>' wasn't found. Error code: 104100 / EntityUserFailure

This blocks using one parameterized dataflow for multiple tables with different schemas.

Request: Re-evaluate the destination table columns at runtime so parameterized destination tables work when columns differ.