Add per-table "BINLOG_ROW" 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 BINLOG_ROW per-table option (values DEFAULT, YES, NO).

From a performance point of view, statement based binary logging is not optimal for tables that does updates where the master has to scan a lot but only updates a few or inserts of many rows with generated auto-increments.

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

If this option is ON for any table, row based binary logging will be used