decoppling of termtagging and normal system work

These mechanisms are only triggered, if termtagging is used for the task:

• XliffTermTagger will run as a REST-Service, potentially on a different machine
• via configuration different REST-URIs for termTagger can be configured for termTagging done at import time and termTagging done after segment-saveing and when opening a segment which is not tagged already
• no termTagging is done any more during import time directly
• a fork is started at the end of the import, which tags all segments of the task by pulling the segments directly from the database and sending them to the termTagger (X segments should be passed at a time to termTagger for less REST-Overhead. More segmens should not be passed at a time in order to have already the first segments tagged shortly after import and be able to start working on the task)
• the termTagger directly returns the html-syntax for term-markup needed by translate5
• translate5 knows on segment-level, if a segment is tagged already.

If no termTaggers are configured, translate5 behaves as if now tbx-files are passed in the task. In addition a warning is logged to error_log

Eva sends test.tbx by end of October