fix: only keep latest e2e test results

[zomars]

What does this PR do?

To avoid reaching GitHub Pages size limits we now only keep the latest e2e test result per each branch.

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have added a Docs issue here if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

• Are there environment variables that should be set?
• What are the minimal test data to have?
• What is expected (happy path) to have (input and output)?
• Any other important info that could help to test that PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
cal	⬜️ Ignored (Inspect)			Aug 19, 2024 11:03pm
calcom-web-canary	⬜️ Ignored (Inspect)			Aug 19, 2024 11:03pm

[zomars]

• fix: only keep latest e2e test results #16273 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @zomars and the rest of your teammates on Graphite

[graphite-app]

Graphite Automations

"Add foundation team as reviewer" took an action on this PR • (08/19/24)

1 reviewer was added to this PR based on Keith Williams's automation.

[github-actions]

E2E results are ready!

• Attempt #28813.1 results