ci: retry flaky test when running in Windows with Webpack

[BobbieGoede]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Since we know that it is flaky and it does succeed after retries, this is preferable over triggering the retry manually. This possibly needs to include the following test "expect scroll to top on nested pages" as well, but I haven't tested its flakiness.

While retries are not ideal, it's better/faster than rerunning the entire job. Hopefully we can find the source of its flakiness someday or someone manages to provide a reproduction with the issue.

Besides this scroll to top test, test/basic.test.ts > component islands > test client-side navigation may be the last remaining flaky test.

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.