Problem

The name "tag handler" does not fit well and it is not understandable to the users. We should change this to more suitable ex: tag conversation dialect. Also we should revoke the configuration for the tag dialects for tms and term collection and make the tag handler static for those resources. For mt's (ai included) the tag dialect should be configurable on resource level with pre-defined defaults. For this we need to add new settings panel in the resources edit/add window or re-use the current one used for AI only resources and add the tag dialect options there as dropdowns.

Solution

Multiple additional changes are required in our tag handler.

1. Rename tag handler UI references (configs, labels etc..) to Tag conversation dialect
2. For TMs and TermCollections we remove the configurable tag handler option and we define the tag handler fro those resources on code level
3. Make the AI settings window generally available also for MT's. In this window we add dropdown with selectable tag - handler (tag dialect) where the default is pre-set with the config mentioned below
4. For MT and ai resources, we remove the client and task overwrites. We introduce or we rename the current tagHandler config for those resources to system default. And this option will be pre-set for the resources.