General overhaul of translation retrieval and storage

What needs to be remodeled?

The way in which each SCThing is translated, and the retrieval of translations.

How is the current model not sufficient?

Right now each property of every instance that extends SCThing has to be translated individually. The same applies for properties that themselves are extending SCThing . In addition only the matching SCThingMeta class can translate the SCThing correct way. This itself is obscure and redundant in usage.

Further more an meta class extending SCThingMeta can only translate properties at the first nesting level.

Last but not least static translations of property names and literal string types are unavailable if the interface extends one or more interfaces from /src/core/base

Which changes are necessary?

Introduce an translation method which is

1. interface independent
2. complete
3. easy to use for developers
4. efficient

Do the proposed changes impact current use cases?

TBA