ci: Adjust re-tries for Wasm tests

[Youssef1313]

GitHub Issue (If applicable): closes #

PR Type

What kind of change does this PR introduce?

What is the current behavior?

What is the new behavior?

PR Checklist

Please check if your PR fulfills the following requirements:

• Docs have been added/updated which fit documentation template (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Validated PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Associated with an issue (GitHub or internal) and uses the automatic close keywords.
• Commits must be following the Conventional Commits specification.

Other information

Internal Issue (If applicable):

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-17058/index.html

[jeromelaban]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-17058/index.html

[jeromelaban]

The benchmarks fail because they run twice, and System.IO.IOException : The file '/__w/1/a/benchmarks/wasm-automated/results/SamplesApp.Benchmarks.Suite.Windows_UI_Xaml_Controls.UIElementPerf.UIElementCreationBenchmark-report.asciidoc' already exists.

It's surprising that the script allows for a second run in that case.

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-17058/index.html