Fix similarity distribution in JPlagResult

[tsaglam]

This PR fixes a bug where the similarity distribution in JPlagResult deviated from the API specification.
The distribution was returned in reverse order (100% to 0% instead of 0% to 100%).

JPlag/core/src/main/java/de/jplag/JPlagResult.java

Lines 108 to 115 in 6fc9f77

	/**
	* For the {@link SimilarityMetric#MAX} that is built in to every {@link JPlagComparison}, this returns the similarity
	* distribution of detected matches in a 10-element array. Each entry represents the absolute frequency of matches whose
	* similarity lies within the respective interval. Intervals: 0: [0% - 10%), 1: [10% - 20%), 2: [20% - 30%), ..., 9:
	* [90% - 100%]
	* @return the similarity distribution array. When JPlag was run with the {@link SimilarityMetric#MAX}, this will return
	* the same distribution as {@link JPlagResult#getSimilarityDistribution()}
	*/

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication

[JanWittler]

Code overall looks fine for me.
Why did you choose to reverse the similarity order for the JSON serialization instead of serializing in the "normal" order and simply inverting the displayed order in the report viewer? As a bonus, we could even add fallback for previous versions in the report viewer by inverting the distribution if a version tag of 4.0.0 is detected.

[tsaglam]

did you choose to reverse the similarity order for the JSON serialization instead of serializing in the "normal" order and simply inverting the displayed order in the report viewer?

To save time and not interfere with the report viewer student, but of course, that's a workaround, and in the long way, the report viewer should just display it the right way.

As a bonus, we could even add fallback for previous versions in the report viewer by inverting the distribution if a version tag of 4.0.0 is detected.

I like that, I will add it to the report viewer issue!