feat: Check Grouping per File

[Chezka109]

Description:
Currently, when GatorGrade runs checks, it lists them without grouping by the file in which they are being run. This makes it harder to identify which checks belong to which file, especially when dealing with a large number of checks across multiple files.

Expected Behavior:
When GatorGrade runs, the checks should be grouped by the file they pertain to. For example:

File: questions/question_one.py:
      ✔  Check 1: Passed  
      ✘  Check 2: Failed  

File: main.py  
       ✔ Check 1: Passed  
       ✔ Check 2: Passed  

This organization improves readability and makes it easier to debug issues.

Actual Behavior:
All checks are listed sequentially without clear indication of which file they belong to. This lack of grouping can make the output hard to interpret, particularly for complex projects.

Proposed Solution:
Modify the logic in output.py to organize checks by file. The solution involves:

1. Identifying which file each check corresponds to during the check process.
2. Grouping and formatting the output in output.py to display checks under the respective file name.
3. Testing the implementation to ensure that grouped output displays correctly for various project structures.

[Chezka109]

@dyga01, here is the issue for the Check Grouping feature we talked about in class today!

[dyga01]

@Chezka109 Thanks for making this issue per our discussion in class. I think that we now need to determine how the checks should be grouped. I could try and allow for instructors to add an option called group that would allow instructors to group checks themselves and then display the rest of the checks being displayed as "other". What do you think about this?