ColumnStore-aware routing

Given an HTAP configuration where the same data exists in two different tables, one created with InnoDB and another with ColumnStore, evaluate the query to see if it contains analytical functions. If it does, rewrite the query so it uses the ColumnStore table.

This assumes an adopted/configurable convention for HTAP. For example, for every InnoDB table, there is an equivalent ColumnStore table with "_hist" appended to it. Resulting in something like this:

tbl_customers (InnoDB)
tbl_customers_hist (ColumnStore)

Applications always query tbl_customers, but if the query contains an analytical functions, rewrite the query to use tbl_customers_hist instead.

The goal is to optimize performance by executing analytical queries on the ColumnStore version of HTAP tables. It could of course be an option customer can enable or disable.