Throw a "data too large" error in ListMapper when parsing data bigger than a certain size like 100MB

[jaclync]

Why

When the response size is large like in the support case in WOOMOB-607 with a large amount of product metadata, the UI could become unresponsive. Other than moving the response parsing to a background thread, the client can also prevent the app from taking up unexpectedly large amount of device resources in case of receiving exceedingly large data.

TODO: still figuring out a way to show appropriate error UX, and maybe disable max size check by default.

Description

Steps to reproduce

Testing information

Screenshots

---

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

[dangermattic]

	1 Message
📖	This PR is still a Draft: some checks will be skipped.

Generated by 🚫 Danger

[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	30578
	Version	PR #15780
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	590505c
	Installation URL	1f5o8321e6ri8

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

[wpmobilebot]

Version 22.7 has now entered code-freeze, so the milestone of this PR has been updated to 22.8.

[wpmobilebot]

Version 22.8 has now entered code-freeze, so the milestone of this PR has been updated to 22.9.

[wpmobilebot]

Version 22.9 has now entered code-freeze, so the milestone of this PR has been updated to 23.0.

[wpmobilebot]

Version 23.0 has now entered code-freeze, so the milestone of this PR has been updated to 23.1.

[wpmobilebot]

Version 23.1 has now entered code-freeze, so the milestone of this PR has been updated to 23.2.