TermPortal: Match-resource like server-side interface

Currently terminology for usage in translate5 tasks (termtagging and usage for pre-translation and concordance search) and the TermPortal is directly interacting with translate5 DB through the back-end of translate5.

This should be changed so that the language resource interface is used for that.

So the concept should allow to implement and select then on languageResource level, which type of term resource is used: a translate5 termcollection or some other kind of term resource (getting its data internally) via API from elsewhere.

Basically this means, that the language resource middle ware layer is used in translate5 for terminology within the application, to get data from different potential data sources.