Eliminating need for XML SAX and DOM 2 in base Java module

Reading of exported preferences yields the same results if done via DOM as well as nanoXML parser

Simple output of Preferences is the same as the original one via DOM

By default (when no XML SAX and DOM 2 present) parsing the properties stream with simple nanoXML parser

Providing 1/4 of default implementation for XML operations from java.util.** and verifying that its behaviour is similar enough with the original implementation based on DOM

Using code injection to separate XML related operations on Properties and Preferences outside of base module. Default implementation is still missing.

Starting work on eliminating XML chunks from base Java

Introducing tools module

Merging eliminateswing branch, as the swing (and AWT) seem to compile separatelly

All parts of the code compile after the 'client' separation