Clean up block templates after running e2e tests

[Aljullu]

Changes proposed in this Pull Request:

Closes #44445.

As discussed in #44363 (comment), if one test failed in our e2e tests related to block customization, it might leave customized templates lingering around, polluting new tests. This PR cleans up block templates in an afterAll().

How to test the changes in this Pull Request:

Note: no need to test this for the release.

1. Verify e2e tests pass.

Changelog entry

• Automatically create a changelog entry from the details below.

Significance

• Patch
• Minor
• Major

Type

• Fix - Fixes an existing bug
• Add - Adds functionality
• Update - Update existing functionality
• Dev - Development related task
• Tweak - A minor adjustment to the codebase
• Performance - Address performance issues
• Enhancement - Improvement to existing functionality

Message

Comment

[github-actions]

Hi @ObliviousHarmony, @thealexandrelara,

Apart from reviewing the code changes, please make sure to review the testing instructions as well.

You can follow this guide to find out what good testing instructions should look like:
https://github.com/woocommerce/woocommerce/wiki/Writing-high-quality-testing-instructions

[github-actions]

Test Results Summary

Commit SHA: c10e4f5

Test 🧪	Passed ✅	Failed 🚨	Broken 🚧	Skipped ⏭️	Unknown ❔	Total 📊	Duration ⏱️
API Tests	259	0	0	2	0	261	0m 37s
E2E Tests	308	0	0	13	0	321	6m 59s

---

To view the full API test report, click here.
To view the full E2E test report, click here.
To view all test reports, visit the WooCommerce Test Reports Dashboard.

[thealexandrelara]

Great improvement for our e2e tests, thank you for working on this! 🙌