Development: Reduce for-dashboard payload significantly when participation results exist

[krusche]

Checklist

General

• I tested all changes and their related features with all corresponding user types on a test server.
• I chose a title conforming to the naming conventions for pull requests.

Server

• Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
• I followed the coding and design guidelines.
• I documented the Java code using JavaDoc style.

Client

• Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data.
• I followed the coding and design guidelines.

Motivation and Context

For each participation result, the for-dashboard REST call includes the whole data again, because of the chain "result -> participation -> exercise -> course -> exercises -> studentParticipations -> submissions -> results". In the worst case, this could result in a 80x larger payload in case a student participated in 80 course exercises.

Description

I created a new DTO because basically just 3 values are needed in the client: score, rated, participationId

Steps for Testing

1. Open Artemis and navigate into the course statistics
2. Double check there are not Typescript errors in the console related to the changes in this PR
3. Make sure the statistics are still the same as before (when e.g. deploying develop)

Review Progress

Performance Review

Code Review

• Code Review 1
• Code Review 2

Manual Tests

• Test 1
• Test 2

[jakubriegel]

Code LGTM 👍🏻

Locally it works: no console errors, stats same as on develop

[github-actions]

❌ Unable to deploy to test servers ❌

The docker build needs to run through before deploying.

[Strohgelaender]

Payload on TS1 is much smaller now:

[terlan98]

Tested on TS5. The course statistics page works as before 👍. There are no Typescript console errors related to this PR.

Code also LGTM.

[JohannesStoehr]

Aprove code

[TimOrtel]

Code looks good to me. This will most likely also require changes within our native clients.

[tobias-lippert]

Tested on ts5.
No typescript errors are shown in the console and statistics are correct.

[maximiliansoelch]

Code looks good to me. This will most likely also require changes within our native clients.

@terlan98 Do we need changes directly in Themis or only in the artemis-ios-core-modules?

[terlan98]

Code looks good to me. This will most likely also require changes within our native clients.

@terlan98 Do we need changes directly in Themis or only in the artemis-ios-core-modules?

Themis is not affected by the changes on this PR. I'll just apply this change on ArtemisCore.