Enhance generated rules coding style

[MartinLoeper]

The generated rules are not clear. This is caused by canonical names for the lookups instead of simple class names being used.

Replace the canonical names by simple names. In order to do this, replace the xTend FOR loop with a java one in order to used the guillemets as usual.

[MartinLoeper]

I should talk to Dominik because I do not know how to call the code inside:

«FOR x : rule.lookups»
    «x.generateCodeForRule(theClass)»
«ENDFOR»

The method generateCodeForRule(theClass) uses expressions like this: «Stream.canonicalName».
I do not know how to use guillemets because it calls .toString() twice which is not what I expect.

[MartinLoeper]

I found the reason in the Java sources which are generated out of the xTend sources:

    EList<Lookup> _lookups = rule.getLookups();
    for(final Lookup x : _lookups) {
      CharSequence _generateCodeForRule = KampRuleLanguageJvmModelInferrer.this.generateCodeForRule(x, theClass);
      _builder.append(_generateCodeForRule);
      _builder.newLineIfNotEmpty();
    }

However I do not know how to instruct the StringConcatenationClient generation to split the result of the method invocation.