Reimplement term tree editors to implement the general save strategy
Currently term trees save changes in the hierarchy (including new terms/nodes) immediately in the DB. This is against our general save strategy which saves changes only after explicitly pressing the save button.
It also creates huge problems because chnages in the nodes and terms itself are still saved via save button by saving (merging) the full term tree. This seems to lead to inconsistent data under certain circumstances.
Therefore we urgently need to reimplement the save strategy in term tree editors (including the Character Editor which more or less is also a term tree editor).
This is urgent as blocks using the Character-Editor which is a prerequisite for all additivity functionality.
During this reimplementation we also should use TermDtos instead of the whole objects.