feat: achievement system documentation

[LucasFalkowsky]

what was done:
a documentation for the backend has ben implemented inside the common/achievement fonder.

[LomyW]

Nice documentation! 💯

[LomyW]

sure about no relation?

export enum achievement_template_for_enum {
  Course = "Course",
  Global_Courses = "Global_Courses",
  Match = "Match",
  Global_Matches = "Global_Matches",
  Global = "Global"
}"

[LomyW]

It's not just the relationship, is it? It is the entirety of the matches, subcourses, students and pupils DATA that is needed for the initial submission of texts AND to make a reference to course / match / student etc

[LomyW]

sure about the "default value 1"? I think it depends on what value is returned by the formula.

[LomyW]

Suggested change

	| action | the action triggered by this event |
	| action | the action that triggered the event. |

[LomyW]

what do you mean by cache metrics for events ?

[LomyW]

Suggested change

	| <div id="metric.ts">`metric.ts`</div> | functions to create metrics together with their related actions when building the project |
	| <div id="metric.ts">`metric.ts`</div> | Collection of metrics and creation of metrics together with the associated actions when creating the project |

[LomyW]

Suggested change

	| `template.ts` | functions to get all templates presorted by group or metrics and to get templates with a certain metric |
	| `template.ts` | Cached templates, sorted by groups or metrics, and to retrieve templates with a specific metric |

[LomyW]

I'm not so sure about this description part, its not why the achievement systems works like this, not because of the new achieved achievement notification. It works because we use also the actions that are also used in the notifications system and we reuse this logic, and store actions in the metric.

This is working since achievements that have newly matched their conditions are announced as a notification, therefore naturally being linked to an action taken call