Frontend incidents table

[aileenr19]

With the new incident structure, the frontend needs to be updated to match. Additionally, staff need a table to track individual incidents with sorting, filtering, etc. functionality.

Changes:

• New incident DTO models
• Student view updated with new models
• Incident info chip updates with new models
• Incidents table created along with description sidebar

Closes #246.

[github-actions]

Test Results Summary

551 tests  ±0   551 ✅ ±0   38s ⏱️ -1s
  1 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit 319b565. ± Comparison against base commit 46dbc32.

♻️ This comment has been updated with latest results.

[naasanov]

I was able to Cmd + Shift + F "complaint" in frontend/src and find several places where the frontend was not updated to the new incident structure. I realize now I for some reason only mentioned updating the student view incident tracking, so thats my bad, but nonetheless the motivation of the ticket was to fully update the frontend.

Partially a reason these were not caught is that typescript did not catch them even though the IncidentSeverity type was not updated, due to these instances not being hooked into the shared types or due to explicit casting. As you go through and update, please also make sure they are fixed to prevent regression

[naasanov]

Also seeing new merge conflicts after other stuff got merged in

[naasanov]

You may have Ctrl + F 'd and updated a lot of the backend. That is outside the scope of this ticket and being handled by another ticket, and I believe that is what caused the test failures. You can revert the backend changes

[naasanov]

lgtm