[Testing] Fix for flaky test(PullToRefreshWorksWhenEnabled) in CI

[NafeelaNazhir]

This pull request improves the reliability of the pull-to-refresh test in Issue30690.cs by adding retry logic and more robust verification for the refresh completion. The main change is to ensure the test does not fail due to transient issues with the pull gesture or UI timing.

Test robustness improvements:

• Added a retry loop to attempt the pull-to-refresh gesture up to three times, increasing the likelihood of a successful refresh in case of intermittent failures.
• Enhanced the gesture by specifying ScrollStrategy.Gesture, a high swipe percentage, and a defined swipe speed for more consistent interaction.
• Improved verification by waiting for both "Refreshing..." and "Refresh completed" statuses, and only passing the test if refresh succeeds within the retries.

[jsuarezruiz]

/azp run MAUI-UITests-public

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Copilot]

Pull Request Overview

This PR improves the reliability of a flaky UI test for pull-to-refresh functionality by adding retry logic and more precise gesture parameters. The test was failing intermittently in CI due to timing issues and unreliable gesture recognition.

Key Changes

• Added retry loop with up to 3 attempts for pull-to-refresh gesture
• Enhanced gesture parameters with specific scroll strategy, swipe percentage, and speed
• Improved error handling with try-catch block around verification steps

[Copilot]

Catching all exceptions with a generic Exception handler can mask important errors. Consider catching specific exceptions related to timeout or element not found scenarios, or at minimum log the exception details for debugging purposes.

Suggested change

	catch (Exception)
	{
	// Refresh not completed yet, will retry
	}
	catch (WebDriverTimeoutException ex)
	{
	// Refresh not completed yet, will retry
	TestContext.WriteLine($"Timeout waiting for refresh: {ex.Message}");
	}
	catch (NoSuchElementException ex)
	{
	// Element not found, will retry
	TestContext.WriteLine($"Element not found during refresh: {ex.Message}");
	}
	catch (Exception ex)
	{
	// Unexpected exception, log details
	TestContext.WriteLine($"Unexpected exception during refresh: {ex}");
	}