[UI Tests] Disable Auto Fill Passwords for UI Tests

[tiagomar]

Description

The objective of this PR is to disable Auto Fill Passwords under Settings for UI Tests to avoid the burden of dealing with the Save Password prompt, which is handled now in regular runs but it's heavily impacted by the long delays during Login perceived in CI (analysis available below).

iPad FAIL/PASS analysis

iPhone FAIL/PASS analysis

Testing

• UI Test steps in CI should be 🟢.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress Alpha by scanning the QR code below to install the corresponding build.

	App Name	WordPress Alpha
	Configuration	Release-Alpha
	Build Number	pr21034-628f6e9
	Version	22.7
	Bundle ID	org.wordpress.alpha
	Commit	628f6e9
	App Center Build	WPiOS - One-Offs #6327

Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack Alpha by scanning the QR code below to install the corresponding build.

	App Name	Jetpack Alpha
	Configuration	Release-Alpha
	Build Number	pr21034-628f6e9
	Version	22.7
	Bundle ID	com.jetpack.alpha
	Commit	628f6e9
	App Center Build	jetpack-installable-builds #5354

Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

[jostnes]

Thanks for making this change @tiagomar! Tested it out locally, and it works as described.

While this still depends on UI interaction (I know you're working on a V2, super looking forward to that!), this is an improvement to the current implementation where we anticipate and wait to dismiss the pop-up on multiple screens.

[mokagio]

Thank you for implementing this @tiagomar !

It's a neater solution than my previous patch to conditionally dismiss the prompt. It should also remove the delay introduced by checking for the prompt every time.

• Have you considered implementing the function at the UITestsFoundation framework level? That would automatically ensure both UI tests targets have access to it, regardless of what will happen to the target membership of UITests/Utils/XCTest+Extensions.swift
• I wish there was a "before all test cases" where we could put this call, as I think it's should be required only once (unless we reset the Simulator between tests, which I don't believe we do). NSPrincipalClass might be a promising avenue.

[tiagomar]

Thanks for checking and commenting, @mokagio! Especially for the nice tip around NSPrincipalClass.

I have this draft PR (still waiting for the tests to run in CI) that addresses both points.