Application password experiment: Fall back to Jetpack proxy after app password generation fails

[itsmeichigo]

Closes WOOMOB-16079

Description

This PR updates error handling for application password generation by catching the failure to fall back to Jetpack proxy requests. Changes include:

• Updates RequestProcessorDelegate to remove the reason in the delegate method.
• Updates RequestsProcessor to only notify failure of application password generation upon catching errors directly related to application password.
• Updates AlamofireNetwork to catch AFError.requestAdaptationFailed and enable retrying requests when this error occurs.

Testing steps

Follow the instructions in TC3 and TC6 of the test plan pe5sF9-4Am-p2.

Testing information

Tested the following test cases with simulator iPhone 16 iOS 18.2.

Screenshots

No UI changes.

---

• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

[wpmobilebot]

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

	App Name	WooCommerce iOS Prototype
	Build Number	pr16079-0af25e0
	Version	23.2
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	0af25e0
	Installation URL	64qmsnvupk2p8

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

[RafaelKayumov]

For the TC3 I got:

{
  "error": "application_passwords_disabled",
  "message": "Application passwords are not available."
}

Requests fell back to the JP proxy.

For the TC6 I got:

{
  "error": "general_error",
  "message": "Application passwords is not working."
}

The above error was returned couple times after every order lost loading attempt. I did 2 or 3 order list reloading by triggering pull-to-refresh. Then it crashed on the 3rd attempt:

Could be a race condition with a parallel retriedJetpackRequests object removing in separate threads. I'm able to reproduce by pull-to-refreshing dashboard and order list in parallel. Repro rate ~15%. Hard to reproduce.

[dangermattic]

	1 Warning
⚠️	This PR is larger than 300 lines of changes. Please consider splitting it into smaller PRs for easier and faster reviews.

Generated by 🚫 Danger

[itsmeichigo]

Great catch @RafaelKayumov! It's a noob error to update those array/dictionary for error handling in different threads. I moved all error handling to a separate file and use sync access to avoid race condition. I also added tests to confirm thread safety. Let me know if you have any other suggestions!

[RafaelKayumov]

Thx!