Extend UML2SCT transformation to handle target language specific types

[laszloItemis]

The code generation is prepared to do so, but the UML2SCT transformation currently only "copy-pastes" the types from the EA model,
which results in not resolvable types if the transformed CREATE model's domain is set to the target language (Java or C).

This doesn't affect the generated code, but it doesn't fully capitalize on the capabilities of the tool (e.g., Initialization expression, language-specific types, etc...).

[paphko]

The code generation is prepared to do so, but the UML2SCT transformation currently only "copy-pastes" the types from the EA model,
which results in not resolvable types if the transformed CREATE model's domain is set to the target language (Java or C).

Then we should add a comment to the model to indicate this issue.
I can do this:

[paphko]

The comment in the model and the current solution is just a workaround and proper solution is still do be done.