Missing .result file update.

Review fixes:
 - Coding style
 - Fix bad .result file
 - Fix test to be tolerant of different timing.
 - Fix test to give better info in case of unexpected timing.

Merge branch 'mdev-6981-master_gtid_wait-status-variables' of https://github.com/openquery/mariadb-server into danblack

Conflicts:
	sql/mysqld.cc

Replaced all references to LINT_INIT with UNINIT_VAR and LINT_INIT_STRUCT.
Removed LINT_INIT macro.

to my_convert_fix() - a new function in /strings.

Checked for missing synonims, added those found.

Problem was that we considered the point itself as the 'border' object. Instead
of that the 'border' of a POINT is an empty set, and the point is the 'interior'.
Another error fixed by the way - not all operations of the resulting function were properly
allocated.

Need to take into account cases of a polygon shaped as a very thin line.

The variables now return real values. They can't be made usual variables because they do not have DEFAULT value.

Problem was in reinitialization of first_successful_insert_id_in_prev_stmt_for_binlog after setting variables.

The problem is in the IsSimple function. If the first and the last points
of a curve coincide it's and exception and the line is still 'simple'.

Index names were not formatted correctly.

The 'srid' field's copying was missing in the copying Create_field::Create_field() constructor.

Merge from Percona Server enforced use of a specific storage engine
authored by Stewart Smith.

Modified to be session variable and modifiable only by SUPER. Use
similar implementation as default_storage_engine.

- Renaming Item::is_bool_func() to is_bool_type(), to avoid assumption
  that the item is an Item_func derivant.
- Deriving Item_func_spatial_rel from Item_bool_func rather than Item_int_func

fixed embedded server tests
MDEV-7009: SET STATEMENT min_examined_row_limit has no effect
MDEV-6948:SET STATEMENT gtid_domain_id = ... FOR has no effect (same for gtid_seq_no and server_id)

old values of SET STATENENT variables now saved in its own Query_arena and restored later

the problem was in assigning default value during parsing.

MASTER_GTID_WAIT function needs some status to evaluate its use.

master_gtid_wait_count indicates how many times the function is called.
master_gtid_wait_time indicates how much time in microseconds occurred
waiting (or timing out)
master_gtid_timeouts indicates how many time times this function timed
out rather than all successful gtids events being available.

This counts the number of times a replication event is ignored
due to slave_skip_errors.

(changes of backported patch are very small: strlen removed, error processing fixed, view open statistics added)

Double error reporting removed.

* watch for "redefined macro" warning
* don't enable -D_FORTIFY_SOURCE=2 in debug builds (it requires -O)

common parent class for Item_func_isnull and Item_func_isnotnull

Add holder thread_id, file_name and line to output.

MDEV-7025 ANALYZE SELECT/INSERT/UPDATE/DELETE from a view does not check access permissions on the view

Added access checking for the ANALYZE statement command.