Add few testcases for the xUnit work

Add a bunch of XML files:

0X-foo.xml :                Original, sanitized test journals
0X-foo-xunit-golden.xml :   Target xUnit representation of the appropriate
                            journals.
01-libica-xunit-manual.xml: Manually crafted xUnit with further notes on
                            BeakerLib <--> xUnit relation
Add testing infrastructure for XSLT

This testing infrastructure focuses solely on the correctness of the
XSLT transformation of BL journals. It does not deal with testing that
xUnit results are actually produced by some BL functions.
First working interation of xUnit XSLT

The transformation is build along the following rules:

Single BL testcase translates to xUnit <testsuite> element, allowing
aggregation of multiple BL test case runs into xUnit <testsuites>
element.

BeakerLib header records are translated into <testsuite> element
attributes, where appropriate attribute exists (id, testname, hostname,
package). The rest is translated to xUnit <property> element. The XSLT
rules for these seems rather sloppy: perhaps there is a better way how
to represent this rule (because these rules are almost identical except
for the key), but I did not find it.

BeakerLib phases translate to xUnit <testcase> elements, with a name
mapping to the element attribute. This means the name does not need to
be unique after translation. I do not know if this is okay in xUnit.

xUnit records just FAILs, not PASSes. BL <test> elements are translated
to either <failure> or <error> xUnit elements only if their content is
FAIL. The phase type affects whether a <failure> or <error> is used. For
FAIL (testing) phases, <failure> is used. For WARN (setup and cleanup)
phases, <error> is used.
Wire the xUnit production to BL

Add the XSLT (using xsltproc) transformation to rlPhaseEnd and
rlJournalEnd functions, which either submit the file using the harness,
or report the location of the file if run locally.
Do not check patches for tempfiles

Perhaps this check should be now deprecated?
Add a new header record for 'pkgdetails'

Some BL journals will contain <pkgdetails> tag in their header. It
should also be translated to a xUnit <property> tag.
Generate errors and failures only for failed assertions

The earlier version translated *ALL* <test> elements to <failure> and
<error> elements, no matter if the original element represented failed
or passed assertion. This fix makes the XSLT translate only those <test>
elements which represent FAILed assertions.
Switch <error> and <failure>

I have tried to display the xUnit results in Eclipse JUnit viewer, and
the results were interpreted differently than I expected:

<failure> is blue, having "test did not work correctly" semantics
<error> is red, having "test worked correctly, found bug" semantics

So I adjusted the XSLT so that WARN phases produce <failure> tags and
FAIL phases produce <error> tags.