Batch import into multiple collections

If no -c argument is given ItemImport checks if a file named
'collections' exists inside the directory of each item.

This file must contain either the handles or the numeric ids of the
collections, one per line. The item is added to all those
collections. The collection specified in the first line is the owning
collection.
Added code to handle edge case

If one of the 'collections' files contains a handle or an id that cannot
be resolved to a collection, the specific item is skipped but the
procedure continues with subsequent items.
Bug fix for multiple import

If a collection could not be resolved the logic would add the item in
the same collections it added the previous item.
BTE option for import works for per item collection list

A new version of BTE (0.9.2.5) needed to be released. This release fixes
some minor bugs in DSpaceOutputGenarator and adds the collection per
item handling.
Resume --resume or -R can now be used with bte import
Added some documentation
ui support for native batch import
more on ui batch import
display batch imports in myDspace
close mapfile
ui support for batch import delete/resume
fix issue with closed contexts
Fixed NullPointer exception in batch import
some fixes and new display messages
merge batch metadata import (via BTE) with batch import via Simple Archive Format
code refactoring
add missing license header
Merge branch 'DS-2177-JSPUI-batchimport' into master