update docs to match code

this limit applies to both 32 and 64-bit VMs

When using CHAR(N) in PostgreSQL any inserted value smaller than N
characters will be right-padded with spaces to fill all N characters.
See: https://www.postgresql.org/docs/9.1/static/datatype-character.html

This change adds an additional Mode.padFixedStrings and set it to true
in the PostgreSQL Mode. Any value converted to a ValueStringFixed at
INSERT will be right-padded with spaces.

For additional infos see the H2 Google Groups post:
https://groups.google.com/forum/#!topic/h2-database/Luaxdrl137Y

use a set to keep track of the tables we need to analyze.
Perform the analysis after we have committed the main transaction, so we
don't hold table locks for any longer than necessary.

In order to make the doc generation for #476 working I had to fix some
errors in existing files. These cover

 - lines which are too long
 - incorrect indentation
 - invalid markup
 - missing javadoc

* Custom data types handler

* Updated doc, changelog, dictionary. Fixed review comment.

* Extended the custom types handler interface

* Fixed test

* Fixed review comments

* Added note on ABI stability of the feature to docs

* Added WITH to CREATE SCHEMA to supply default TableEngine params

* Updated docs to reflect changes in CREATE SCHEMA

* Review fixes - docs; code de-duplication; test for table engine params in schema

* Setter for table engine params in Schema

Currently the JDBC type of TIMESTAMP WITH TIME ZONE is Types.OTHER.
JDBC 4.2 has a dedicated type for this Types.TIMESTAMP_WITH_TIMEZONE.

Unfortunately this type is only available in JDBC 4.2/Java 1.8 so I
hard code the constant value instead of the constant reference.

we don't seem to be keeping this up to date anymore

Some PRs merged into 1.4.193 and 1.4.194 are missing from the
changelog.