Annotations for tracking log statements

We should add annotations for both Python and Javascript tracking log statements so that we can generate reports between releases to document which events have been added / removed / changed, where they are being emitted from, and confirm that those changes do not break downstream reporting.

We should at least include the event name and description thought it would be ideal to capture the fields, types, and descriptions so that we can automatically create documentation like we have been doing manually:
https://docs.openedx.org/en/latest/developers/references/internal_data_formats/tracking_logs/student_event_types.html

This would involve:

• Adding a new config type for tracking events
• Adding a new Sphinx extension to render the documentation
• Updating docs.openedx.org to use the new documentation to replace the event reference
• Creating a tool to generate reports across repositories in the openedx org

Commencez par les types de configuration existants dans code_annotations/contrib/config et les extensions Sphinx dans code_annotations/contrib/sphinx/extensions. Définissez les exigences d’annotation pour les noms d’événements, les descriptions, les champs, les types et les descriptions, puis examinez la documentation de référence des événements liée et planifiez l’outil de génération de rapports inter-dépôts ; le travail est considéré comme terminé lorsque la documentation générée et les rapports de release peuvent remplacer la référence manuelle actuelle des événements.