API graphql: expose les demandes de corrections

[colinux]

• - renomme DossierCorrection#{kind =>reason} ainsi que sa valeur par défaut correction => incorrect, ce qui permet des méthodes de type correction.dossier_incorrect? ou correction.dossier_incomplete?
• - l'API expose dateDerniereCorrectionEnAttente au niveau du dossier et le type de correction et sa date de résolution au niveau du message associé
• Créer une correction en envoyant un message
• Filtrer les messages pour n'avoir que les demande de correction ? ça me paraît inutile pour le moment

Remarque
La seule différence entre incomplete et incorrect est dans le traitement du SVA, donc dans notre interface instructeur, on expose incomplete uniquement sur les démarches SVA.
Or avec l'API, les 2 types seront exposés pour tout le monde.

[what-the-diff]

PR Summary

• Enhancements to Correction Request Status
  A new classification system is added to categorize correction requests as 'incomplete' or 'incorrect'. This helps track the type of issues users are having more accurately.

• Introduction of the 'last pending correction request' date
  A new field has been added to show the date of the most recent pending correction request from a user. This helps monitor pending requests and their timelines more efficiently.

• Enhancements to Correction Request Tracking
  Keeping track of correction requests is now easier. A change to the default kind attribute makes it easier to identify 'incorrect' correction requests. New tasks and a migration support this change.

• Improved decision date calculation
  The decision date calculation system now takes the new correction types into account. Utilizing these specifics leads to a more accurate and fair calculation of the duration.

• Updated Factory and Tests
  The factory used for testing is updated to include a scenario with a pending correction. Additionally, new tests have been added to check the functionality and robustness of the recent updates.

• Major codebase updates to harmonize with the changes
  Several types, models, and concerns have been updated to fit with the new correction request status classification and 'last pending correction request' date field. New factories and specifications have also been added for these updates.

• Schema updates
  The updates have been reflected in the schema files. These files lie at the core of the project and help keep track of all the project's objects and their relationships.