of 4k or 8k in addition to the default of 16k.  Only one page size is
supported at a time.

A new global startup variable is introduced called INNODB-PAGE-SIZE.

InnoDB maps UNIV_PAGE_SIZE to this setup parameter in order to create
and use all tablespaces with the same page size.  Only 4k, 8k, and 16k
are supported here.  Errors are reported if a tablesapce is opened with
a size other than the current setting.  The page size is embedded into
the tablespace header at location FSP_SPACE_FLAGS.

Extensive changes are made to test cases.  Some are made to run with
16k page sizes only by adding --include include/have_innodb_16k.inc.
Other test scripts are changed to accept multiple possible outputs.
And others are moved to the new tests suite/innodb/innodb_16k, innodb_8k
& innodb_4k.

extra/nnochecksum.c is improved to compile parts of the innodb code
directly, use mysys functions for command line processing, and to use
the embedded page size in FSP_SPACE_FLAGS within each tablespace.

The standard runs that get executed by pushbuild are expanded.  See
collections/ default.push, default.daily & default.weekly.

The following bugs were found and fixed as part of this patch;
Bug#13391699   INNODB_16K DOES NOT PASS THE HIGH LOAD CHECK,
               TRYING TO DO IBUF MERGE TO DROPPED
Bug#13394706   INNODB; SLOW DOUBLEWRITE BUFFER CREATION WITH UNIV_DEBUG
               AND 4K PAGE SIZE
Bug#13391353   INNODB :PAGE SIZE SUPPORT - INNODB_<4/8/16>K.TEST GETS
               ROW SIZE ERROR ON 32 BIT
Bug#13336585   INNODB: CHANGE BUFFERING WITH 4K PAGES CAN ASSERT IF
               SECONDARY KEY IS NEAR MAX
Bug#12602606   INCONSISTENCY IN EXPLAIN SELECT ... WHEN USING 4K PAGE SIZE
Bug#12573796   INNODB; TEST SUITE/INNODB/INNODB_TRX_WEIGHT.TEST DEADLOCKS
               FOR 4K AND 8K PAGES
Bug#12562795   INNODB; CRASH ON WINDOWS WHEN RECOMPILE FOR 4K PAGE SIZE.