Improve E2E Test Failure Handling and Reporting

[shammowla]

Description

1. Test Retries: Added 3 retries for failed tests in Sauce Labs configuration to reduce flaky test failures.
2. Failure Logging: Implemented a step to collect and store test results, especially for failed tests.
3. GitHub Issue Creation: Automated the process of creating GitHub issues for failed tests.
4. Issue Updates: For existing issues, the system now adds details about new failures to the issue.

Changes:

• Updated .sauce/prod-safari.yml, .sauce/prod-firefox.yml, and .sauce/prod-chrome.yml to include 3 retries for failed tests.
• Added a "Get Saucelabs Test Results" step in the workflow to collect test results.
• Created a new script handle-test-failures.js to manage the creation and updating of GitHub issues for test failures.
• Updated the "Handle Test Failures" step in the workflow to use the new script for each browser job.

Related Issue

Motivation and Context

Screenshots (if appropriate):

Types of changes

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

Checklist:

• I have signed the Adobe Open Source CLA or I'm an Adobe employee.
• I have made any necessary test changes and all tests pass.
• I have run the Sandbox successfully.