Support hexad player type event

[MP-DG]

Description of changes

Gamification Service now informs other services of the Player Type of the users.

• sends UserHexadPlayerTypeSet event when the PlayerType is evaluated
• listens to RequestHexadPlayerTypeEvent and sends UserHexadPlayerTypeSet event

How has this been tested?

Please describe the test strategy you followed. If not tested, please explain why.

• automated unit test
• automated integration test
• manual, exploratory test

In case of manual test, please document the test well including a set of user instructions and prerequisites. Each including an action, it's result, and where appropriate a screenshot.

Checklist before requesting a review

• My code is easy to understand
• My code follows the coding guidelines of this project
• My code fulfills all acceptance criteria
• The test coverage (line and branch) is reasonably high, especially on Service classes and other classes with complex logic
• I have made corresponding changes to the documentation or
  the wiki/adr
• I made no breaking changes in the database schema or if so, I will perform a database migration

Checklist for reviewer

• The code is easy to understand
• The code follows
  the coding guidelines of
  this project
• The code is tested or if not, the reason is documented or discussed
• The added and existing tests reasonably cover the code change
• The code has no breaking changes in the database schema or if so, the assignee is aware of it and
  will perform a database migration

[c-neli-r]

Für mich macht der Code einen sehr aufgeräumten und gut strukturierten Eindruck. Ich bin inhaltlich allerdings nicht wirklich in deiner Bachelorarbeit drin, und für die vielen Änderungen war die Zeit zum Durchschauen etwas knapp. Wenn aber alles sauber läuft, würde ich dir auf jeden Fall mein Okay geben.