chore: improve test file cleanup

[sharanyavinod]

Description

• Cleanup test files created immediately after test execution
• Existing logic for cleaning up test files older than 2 hours still kept as a fallback

Related Issue

Fixes #1149

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
In case there are problems, just click the checkbox below to rerun the respective action.

• Re-sync branch

Commits

• c420103 ✅ (latest)
• f87ca99 ✅
• 9780da3 ✅
• b27fb7d ✅
• d0b8025 ✅
• 584292e ✅
• 6ea8c57 ✅

[hannessolo]

Definitely makes sense - only question I have is do we still have an e2e testing deletion via the UI? It would probably make sense to still have a test that covers it.

[sharanyavinod]

@hannessolo Yes, Create Delete Document in edit.spec.js still does delete through UI