Additonal improvement on MSDTC enlistment.

Unfortunately the current pgxalib.dll can't recover transactions which use
sslmode verify-[ca|full] or whose authentication is SSPI, certificate or
ident.
When MSDTC.exe tries to connect to PostgreSQL it does so under Windows user
NETWORKSERVICE, which won't match the username the original user connected
to PostgreSQL as. So PostgreSQL will reject the connection.

In addition XARMcreate() doesn't detect it on enlistment because invoked
xa_open() doesn't connect to the specified datasource. Though it has no
problem unless crash occurs between PREAPARE and COMMIT, the recovery of
the transaction is impossible when such a crash occurs.

Now 3 diffrent behaviors can be speicified using the xaopt connection
string option.

 1: The current default behavior.
 2: Same as above except it simply examines if the recovery for the specified
    datasource is unavailable before calling XARMcreate(). Currently it only
    examines whether the connection uses sslmode verify-[ca|full]. I can't find
    the way to detect SSPI, certicate or ident authentication.
 3: Invoked xa_open() tries to connect to the specified datasource immediately
    as user Network Service.
Add the libpq use parameter to the dtc connection string.
Improve regression test for reading a bytea column to SQL_C_CHAR.

When converting a bytea to SQL_C_CHAR, the driver uses upper-case letters in
the hex output, while the backend uses lower-case letters. That leads to
different output when using bytea_output=hex than with bytea_output=escape.
Set bytea_output explicitly in the regression test, so that it works
regardless of the current bytea_output setting. And test both settings - the
code path taken in the driver is quite different.
Fix SQLTables column names to be ODBC version 3 compliant

In ODBC3, TABLE_QUALIFIER was renamed to TABLE_CAT, and TABLE_OWNER to
TABLE_SCHEM.

David Hedberg
Silence compilers warnings without _HANDLE_ENLIST_IN_DTC_ or USE_LIBPQ.

Compiler complained about unused variable.
Add a new dialog page to the setup program and allow the setting
of PREFERLIBPQ and XAOPT option.
Cleanup the code for *test* button and add the functionality to test
MSDTC support.
Avoid the registry operation to set XADLL entry from wow64 process.
Fix the wrong use of snprintf format in the previous commit.
Add a powershell script buildBootStrapper.ps1 which builds bootStrapper program
with some optional parameters. Quote the version number of bootstrapper from
the configuration xml file unless specified. Also change the name of 32bit MSI
in the bootstrapper according to changes of 32bit installer build system.
Change buildInstallers.ps1 build the bootstrapper together.
Change ALLUSERS from "2" to "1" of the 64bit installer.
Use 1ST, 2ND or 3RD PAGE instead of PREV or NEXT PAGE for the setup
program.
Don't continue to build installers in case the compilation failed.
Suppress option button from the bootstrapper dialog using BalExtention.
Removed a duplicated description.
Removed RESET_CRYPTO_CALLBACKS preprocessor symbol definition.
This is no longer needed and rather dangerous.
The removal also make it possible to remove the dependency to libeay32.
Include pdb files in the contents of installers.
PG_BUILD_VERSION seems no longer needed.
Enable -Wall compile option if it's available.
Fix some differnces in regression test.
1. result-convrsion-test.c
   Explicitly specify an appropriate time zone.
   isprint() doesn't work as expected in my environment. It's safe
   to verify that the parameter is a single byte before calling
   isprint().

2. prepare-test.c
   Explicitly specify "postgres_verbose" intervalstyle.

3. diagnostics.c
   pg_terminate_backend() sometimes succeeds with no error message.
Prep next release version 09.03.0400.