Refactor e2e_eval function in eval_end2end.py for modularity

[sweep-nightly[bot]]

Description

This PR refactors the e2e_eval function in eval_end2end.py to improve modularity and maintainability. The function is broken down into smaller subfunctions, making the code easier to understand and test. The changes include:

• Extracting the code for reading files into a separate function named read_files
• Extracting the code for calculating metrics into separate functions
• Extracting the code for printing results into a separate function named print_results
• Updating the e2e_eval function to call these new functions and handle their returned values

Summary of Changes

• Created a new function read_files to handle reading ground truth and prediction files
• Created separate functions for calculating metrics such as Intersection over Union (IoU) and edit distance
• Created a new function print_results to handle printing the evaluation results
• Updated the e2e_eval function to call the new functions and handle their returned values
• Added unit tests for the new functions to ensure their correctness

These changes improve the modularity and maintainability of the code, making it easier to understand, test, and maintain.

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

[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.