Add per-table "QUERY_CACHE" option

The initial MDEV-37070 scope included 3 per-table options: QUERY_CACHE, ADAPTIVE_HASH_INDEX, BINLOG_ROW.
MDEV-37070 scope was refined: ADAPTIVE_HASH_INDEX became also a per-index option, while QUERY_CACHE and BINLOG_ROW were excluded from the first implementation.
This ticket is opened to track the feature request of the QUERY_CACHE per-table option (values DEFAULT, YES, NO).

From a performance point of view, QUERY_CACHE should not be used with tables that change very frequently.

The effect of the new per-table QUERY_CACHE option would be:

Having this option OFF is the same as using SELECT SQL_NO_CACHE for any query using this table.
Having this option ON is same as using SELECT SQL_CACHE for this table and the query will be cached if no other table has QUERY_CACHE=OFF

As a note, in MDEV-37070 there were suggestion to make QUERY_CACHE automatically toggled per table (link here) as well as counter-arguments in favor of this new per-table option (link here). Please refer to full MDEV-37070 list of comments for further details.