Feature: Sub-Categories for config-file / Grading-Tab

[Shirkanesi]

Is your feature request related to a problem? Please describe.
Currently there is only an option to create different categories for mistake-types that can internally be capped to specific limits.
Therefore using those categories to sort the buttons in the UI is not possible (without losing the penalty-cap).
As the location of buttons will (most likely) change with a change in the config-file, grading quickly gets quite frustrating (as our monkey-brains will initialy memorize the location of certain buttons rather quickly and adapting to a change in the layout takes quite long).

Describe the solution you'd like
There should be an option to additionally group penalty-buttons by logical categories (as "comments", "language", ...) to enforce logical sorting of the buttons and to minimize changes in the layout (as an addition of one button regarding e.g. "comments" only affects relative positions inside this sub-category and all other categories will stay untouched.
In general finding specific buttons will be sped up quite a lot when similar buttons are next to each other.

---

Note: For implementation it should be ensured those changed won't create a breaking change in created feedback but only in the config-files.
(I don't see a reason why this should happen hence only the "shortName" is used for the Feedback-JSON)

[Shirkanesi]

In this process, deserializing the configuration-files could also be cleaned up a bit.

[dfuchss]

Currently, I'm not working on this :)

[Shirkanesi]

We need to discuss about this feature in the future as it is a breaking change in the config-file, so the way this is actually done should be made clear before developing the feature.

[dfuchss]

Is planned to be part of a practical course task this term