Multiple unknown RawLicenses result in only one NormalizedLicense entry

[ohecker]

When multiple RawLicenses exist for an ApplicationComponent which can not be mapped to a known license this results in only one NormalizedLicense entry with UNKNOWN license to be created (instead of one entry für each of them).
Cause is the configured drools rule logic which only creates a new NormalizedLicense if there is no such license entry already existing.
The issue is disturbing because it might result in not the right number of license per component being shown. Nevertheless it is not critical as UNKNOWN licenses need to be handled anyway and will no longer appear when license mapping is completely done.