PHP - XML_XSLT2Processor Files

Release Notes:
This release is a bug fix release. It's main purpose is to provide support for
newer versions of AltovaXML and SAXON that have appeared over time.

Change Log:
== Class changes ==
Support has been added for "SAXON9he" as an XSLT processor. Because of this, the
default version is exactly that one. For future's sake, saxon JAR files will be
expected to be named "saxon*.jar" where "*" is whatever you wrote after "SAXON"
in the first argument of __construct().

Every path starting with "/" is treated as an absolute UNIX filepath
on UNIX systems. On Windows, it still means relative to the document root.
This should (in theory) solve many path related problem on UNIX systems.

The JRE is now looked for manually. Upon failure to detect it,
an exception is thrown. On UNIX, a file named "java" is looked for
in the CWD and %PATH%, and on Windows, a file that is called "java" and has an
extension from the %PATHEXT%.

The __construct() now accepts $processorPath as an associative array with
"processor" and "runtime" as keys, and paths to
the XSLT processor and JRE respectively.

Error codes from AltovaXML2009 and above are now properly placed in the error
object. They were previously visible as part of the message.

All ereg (POSIX) function calls are replaced by equivalent PCRE ones to avoid
E_DEPRECATED warnings in PHP 5.3.

== JAR changes ==
An old attempt to provide support for SAXON on .NET was removed. This is the
main thing that was causing the size of v0.5.2 to be as huge as it was.

The way configuration is handled has been greatly simplified. Previously, the
configuration was recreated at the custom method. This caused issues with
SAXON9he, so in order to avoid them now and in the future, the JAR simply calls
the proper function directly from SAXON, after which it adjusts the defaults.

== Test Suite changes ==
A $processorPaths and $jre variables have been introduced inside the
XML_XSLT2Processor_Test class. Each key in $processorPaths holds the path to the
corresponding XSLT processor/interface, and $jre holds the location of the JRE.

Because there are minor differences from other versions, support for SAXON9he
has been added as part of the test suite.

The test for DISABLE_EXTENSION_FUNCTIONS and STRIP_WHITE_SPACE have been moved
from being SAXON_JAVACLI and SAXON_CLI specific (respectively) to being
SAXON8_JAVACLI and SAXON9_JAVACLI specific plus SAXON8_CLI and SAXON9_CLI
specific. For some reason, SAXON9he, or at least the version I've been testing
with fails those tests.

Due to the change for AltovaXML, the test for getting its errors detects if
"code" is null (as it should be for older versions), and if not, performs a
check against the actual error code received.