Met additional issues while trying to enable it.

information_schema. Added .opt file to enable running this
test as a part of innodb_zip suite and recorded current
correct results.

- Also rename plugin's config file
- And fix unit test's CMakeLists.txt

Copy the detection logic from 'rocksdb' test suite, add a note.

Merge branch 'bb-10.2-mariarocks-wlad' of https://github.com/mariadb/server into bb-10.2-mariarocks-wlad

Default to static release (previously static debug was used in debug
builds, but not is appears to be too slow)

Restore MYSQL_SYSVAR_UINT64_T and MYSQL_SYSVAR_SIZE_T in
plugin.h

They use much more disk space than all other tests in rocksdb test suite

Don't use Perl autodie module as there are platforms where it is not present

fixes many test failures in optimized builds in --ps-protocol

vcols in the table definition are intentionaly bad and produce
warnings when a table is opened. In some cases (depending on the
TDC/TC state as left by earlier tests) a table might be opened in the
middle of the test, resulting in spurious warnings. Suppress them.

Also, don't run main.mdev-504 for ps-protocol at all (instead of
disabling ps-protocol inside the test, but still running the test)

as a plugin can be disabled, so the target doesn't necessarily exist

parse CHECK constraint *before* Column_definition validity checks

Default to static release (previously static debug was used in debug
builds, but not is appears to be too slow)

We are hitting this
https://github.com/facebook/mysql-5.6/issues/569
and we are not ready to merge the fix currently

Restore MYSQL_SYSVAR_UINT64_T and MYSQL_SYSVAR_SIZE_T in
plugin.h

Some Windows enviroments don't have uint64_t, and we dont really need
that type. Assume 64-bit integers take 8 bytes.

that was destroyed in a previous commit

remove hard-coded paths (that assumed we're in a source tree)
remove various shell/perl/awk/whatsnot scripts, use mysqltest and perl
remove numerous --exec /some/unix/tool commands, use mysqltest and perl

1. Special mode to search in error logs: if SEARCH_RANGE is not set,
   the file is considered an error log and the search is performed
   since the last CURRENT_TEST: line
2. Number of matches is printed too. "FOUND 5 /foo/ in bar".
   Use greedy .* at the end of the pattern if number of matches
   isn't stable. If nothing is found it's still "NOT FOUND",
   not "FOUND 0".
3. SEARCH_ABORT specifies the prefix of the output.
   Can be "NOT FOUND" or "FOUND" as before,
   but also "FOUND 5 " if needed.

namely, restart_mysqld_with_option.inc and kill_and_restart_mysqld.inc -
use restart_mysqld.inc instead.

Also remove innodb_wl6501_crash_stripped.inc that wasn't used anywhere.