Correctly show matches when the token order is not line index order

[tsaglam]

In some cases, the first and last tokens of a match are not the first or last elements of the match in the source code. This happens e.g. when:

• view files are used, as in the EMF language module
• the code is normalized before parsing for obfuscation detection
• in rare edge cases, even in normal language modules, e.g., regarding if/else/end-if/try/catch, etc.

In these cases, JPlag was not able to correctly display the matches in the report viewers. This PR fixes this by comparing the line indices of all tokens of a match.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication

[tsaglam]

@smjonas this might help with the issues of showing matches for model instances.
@mbrdl this will probably fix the report viewer issues when enabling your normalization.

[smjonas]

Thanks for working on this! Unfortunately, after rebuilding JPlag with your commit I am still seeing the same issues as before (no highlighting in the report viewer for both language modules).