Refactor tools/end2end/eval_end2end.py for modularity

[sweep-nightly[bot]]

Description

This PR refactors the tools/end2end/eval_end2end.py file to improve its modularity. The e2e_eval function, which was previously large and complex, has been broken down into smaller, more manageable functions. This makes the code easier to understand and maintain.

Summary of Changes

• Extracted the code block for reading the ground truth and prediction files into a separate function named read_files.
• Extracted the code block for calculating the Intersection over Union (IoU) between two polygons into a separate function named calculate_iou.
• Extracted the code block for calculating the edit distance between two strings into a separate function named calculate_edit_distance.
• Extracted the code block for matching ground truth and prediction data into a separate function named match_gt_and_pred.
• Extracted the code block for calculating the precision, recall, and f-measure into a separate function named calculate_metrics.
• Modified the e2e_eval function to call the newly created functions.

Fixes #1.

---

🎉 Latest improvements to Sweep:

• Sweep now uses the rope library to refactor Python! Check out Large Language Models are Bad at Refactoring Code. To have Sweep refactor your code, try sweep: Refactor <your_file>.py to be more modular!
• Sweep finds and fixes bugs in your code by writing unit tests! Check out Having GPT-4 Iterate on Unit Tests like a Human.

---

💡 To get Sweep to edit this pull request, you can:

• Comment below, and Sweep can edit the entire PR
• Comment on a file, Sweep will only modify the commented file
• Edit the original issue to get Sweep to recreate the PR from scratch

[sweep-nightly[bot]]

Sandbox Executions

• [X] Check tools/end2end/eval_end2end.py ⋯

  Sandbox logs for

• [X] Check tools/end2end/eval_end2end.py ⋯

  Sandbox logs for

• [X] Check tools/end2end/eval_end2end.py ⋯

  Sandbox logs for

[sweep-nightly[bot]]

Apply Sweep Rules to your PR?

• [ ] Apply: All docstrings and comments should be up to date.
• [ ] Apply: There should be no trailing whitespace at the end of lines.
• [ ] Apply: Indentation should be consistent throughout the codebase.
• [ ] Apply: Variable and function names should be descriptive and follow a consistent naming convention.
• [ ] Apply: There should be no commented out code in the codebase.
• [ ] Apply: There should be no unused imports in the codebase.