Split 'Terminology > Not found in target' AutoQA-category into 4 categories

Currently, term-tagging for Client is done on Client-side, but this is going to be changed:

1. Terminology will now be imported by Client guys into translate5 as language resource(s) of type TermCollection via importing TBX-file(s), so that terminology will now be stored in translate5-dabatase and maintainable via TermPortal
2. Term-tagging itself will now be done on translate5-side (instead of on Client-side), and this means that TermTagger service which is a part of translate5 installation will be fed with segment batches and terminology during the AutoQA-step of the task import process, e.g. in the same way as it goes for ordinary term-tagging when no Client-specific things are involved
3. Currently, TermTagger-plugin have it’s own logic of how segments (having terms, already tagged by TermTagger-service, if any) are evaluated for AutoQA-qualities, and implementation of this logic does not rely on terms statuses at the moment, but this is what Client wants - see table with descriptions below.

So, the todos list is:

1. Client-side:
   1. ‘Client’-group in the left side AutoQA-panel should be removed, but instead ‘Terminology’-group’s ‘Not found in target (X)’-category should be transformed into expandable sub-group with categories, so that ‘X’ should be = ‘A’ + ‘B’ + ‘C’ + ‘D’:
      1. ‘Admitted (A)’
      2. ‘Preferred’ (B)
      3. ‘Standardized’ (C)
      4. ‘Others’ (D)
   2. Some colors should be applied for terms with those different categories
   3. As additional requirement "Standardized terms" will get their own icon type in right hand termportlet in the editor. The same icon will also be used in the TermPortal, where so far they would have the blue dot for "admitted".
2. Server-side:
   1. TermTagger-plugin’s source code should be adopted to move each of all cases of ‘Not found in target’ into one of above mentioned 4 categories
      1. For backwards compatibility, quality key not_found_in_target used on database-level for ‘Not found in target (X)’-category should be kept as it is but now used to represent ‘Others (D)’-category
   2. Client-plugin’s source code related to glossary/terminology should be removed
      1. Some further discussion might be required for doing that enough precisely
   3. PHPUnit tests which will be affected by this should be identified and fixed
   4. Separate PHPUnit test should be created for testing
3. General: 
   1. No new configs needed, all described changes will be for all users and won’t depend on whether Client-plugin is enabled