termTag tags on the fly, which are loaded untagged to the editor

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

• if segments are loaded in editor, which are not tagged already, Ajax-Requests ask the Server for retagging (X segments at a time; next X segments should be called, when first call is fnished. No parallel calls in order to get the first X segments the fastest as possible and to do no DOS-attack to the server, since termTagger is grapping all CPU-power it can get); what is best for x should be tested; => be carefull of raise-condition with termTagging done by fork of import!!!)
• If a segment which is not tagged is opened by a user, a message is shown, that the user has to wait for termTagging. The segment is sent to the server for tagging on its own, if it is not already part of a tagging call as defined in the previous bullet. Only after tagging is finished, the segment will be opened
• keep an eye on the possibility to disable on import time, that a segment can be edited, if no target terminology is missing (see TRANSLATE-303)