OptimizerHints dropped in favor of SET FORCE_JOIN_ORDER

when we can satisfy a query from an index without touching table data,
then that index should have a lower cost than an index that DOES need
to retrieve table data

OptimizerHints dropped in favor of SET FORCE_JOIN_ORDER setting, fixed join order in case of TableFilter reorderings by Parser, added more tests.

method

Sub-query or view cost could be wrong for cached ViewIndex

Batched index lookups for sub-query

Allow to create custom Row implementations with optimized memory footprint.