[E2E Testing] Fix update e2e bottleneck

[ew3361zh]

Context

Issue(s) closed by this pull request: closes #3224

What

Removes the deepdiff comparison of results from e2e test simulation runs from old expected results in the step prior to overwriting those results as the new expected e2e results.

Why

There has been a bottleneck/outright stall out on certain machines (windows/linux primarily) in updating the e2e expected results. Initial indications were that this was occurring at the deepdiff comparison stage. Upon further investigation and reflection, this comparison is not a value add for the process of updating the expected results so it's been removed here to hopefully speed up the process.

How

In the update expected results code, there was a deepdiff comparison of the results from the run that just completed. This step has been removed here.

Test plan

• Run the update expected e2e results task.
• Check that the results are passing with e2e testing.

Input Changes

Output Changes

• N/A

Filter

[github-actions]

Current Coverage: 99%

Mypy errors on fix-update-e2e-bottleneck branch: 1164
Mypy errors on dev branch: 1164
No difference in error counts

[github-actions]

🚨 Please update the changelog. This PR cannot be merged until changelog_WIP.md is updated.
🚨 Flake8 linting errors were found. Please fix the linting issues.

[github-actions]

Current Coverage: 99%

Mypy errors on fix-update-e2e-bottleneck branch: 1164
Mypy errors on dev branch: 1164
No difference in error counts

[matthew7838]

LGTM, tested and worked as expected. I agree with the trade-off. The removed warning/log/diff files weren't very useful for the e2e update task anyway. Thanks for looking into this.

[allisterakun]

LGTM!

[github-actions]

Current Coverage: 99%

Mypy errors on fix-update-e2e-bottleneck branch: 1164
Mypy errors on dev branch: 1164
No difference in error counts