feat: Refactor the output comparator to consider dropped errors

[bdferris-v2]

Also includes a general refactoring of the report generation logic:

• pull more logic out of Main
• adding specific model classes for JSON serialization

As discussed in #1232.

Please make sure these boxes are checked before submitting your pull request - thanks!

• Run the unit tests with gradle test to make sure you didn't break anything
• Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
• Linked all relevant issues

[bdferris-v2]

@maximearmstrong this is mostly ready for review and I'd love your feedback if you have cycles.

It isn't fully ready to review/commit because I haven't updated the comment_generator.py script yet. That said, I wanted to propose a secondary refactor there as well. The outputcomparator is already producing a block of text to be logged by the output comparator that seems pretty similar to what's being generated by the comment_generator.py script. Maybe we could have outputcomparator just save its log lines to a file and use that in the PR comment, scraping the script entirely?

[maximearmstrong]

Maybe we could have output comparator just save its log lines to a file and use that in the PR comment, scraping the script entirely?

I agree. I think it would also be better from a design standpoint if the output comparator took on that responsibility.

[maximearmstrong]

I've added a few comments, but overall it's great! The new design brings a lot of clarity to the code. Thanks a lot @bdferris-v2!

[bdferris-v2]

I've updated the comment generation code, as discussed. This is ready for final review.

[isabelle-dr]

Thanks for working on this @bdferris-v2 !
I have added a comment above. We might need to update ACCEPTANCE_TESTS.md to reflect the changes in this PR.

What is going to be the schema of the new report with these changes?

[maximearmstrong]

I've approved the PR. Thanks @bdferris-v2!

We might need to update ACCEPTANCE_TESTS.md to reflect the changes in this PR.

What is going to be the schema of the new report with these changes?

@isabelle-dr do we need clarity on these items before merging?

[isabelle-dr]

Thanks Maxime, I think it is in the scope of this PR to update ACCEPTANCE_TESTS.md with the changes (addition of dropped errors, report schema change).

[bdferris-v2]

@isabelle-dr I updated the ACCEPTANCE_TESTS.md to reflect the changes in this PR.

[maximearmstrong]

Perfect! Thanks @bdferris-v2