fixing a bug caused by FITS ambiguities

fixing a bug in the FITS Parser that is caused by an
ambiguity of the FITS schema for the format_version property
when there is a CONFLICT in the identification.

The fix is done by a POST Processing Rule.
adding changelog and gen-script
adding tika adaptor stub

modifying the controller to use the correct adaptor
based on a configuration provided within the map.
removing xml filtering in the gatherer.
adding -i switch in command line

adding the FITS or TIKA config in the command line
adding the first version of the TIKA adaptor

adding a tika adaptor and a tika result parser.
parsing the input files and wrapping them in elements.

adding a tika property mapping file (not complete)
fixing a parser problem

removing dots ('.') from the keys, because
they cause Mongo to fail. Fixing some other minor
issues.
splitting tikas extended mimetype

splitting it into two properties:
mimetype and charset
limiting the known TIKA Adaptor properties

As TIKA is not very well documented with respect to the
supported properties, we limit the currently known properties
by the TIKA Adaptor.

Supported are:
Content-Length=size
Content-Type=mimetype
Content-Encoding=encoding
Content-Language=language
Copyright=copyright
Creation-Date=created
charset=charset
using FITS as default

if no metadata input type is specified, then FITS is used by default
and a WARN log message is outputted
Merge branch 'feature/tika-adaptor' into integration