test: update the LambdaTest iOS element baselines after the visible-part fix

[plum117]

Why

The scheduled cloud run on main (38078263826) failed only in the LambdaTest iOS web job. One test failed on all 6 iOS devices: "should compare an element with ignore elements" (32 % to 53 % mismatch).

This is the baseline change that #1312 announced. Since #1312, an iOS element screenshot of an element that is not fully in the viewport has only its visible part, as on Android. The .features_vqN4 section is taller than the viewport, and the old baselines still had the full element size with an empty part. The cloud jobs do not run for PRs from forks, so #1312 could not update them.

What

The 6 ignoredElementsElementScreenshot-* baselines of iphone_14_pro, iphone_15_pro_max and iphone_17_pro_max (portrait and landscape), from the .tmp/actual images of that run.

Device	Old	New	Old rows with content
iPhone 14 Pro landscape	1914×1908	1914×1007	0–1010
iPhone 14 Pro portrait	891×4446	891×1959	0–1958
iPhone 15 Pro Max landscape	2154×1728	2154×1122	0–1121
iPhone 15 Pro Max portrait	1002×4212	1002×2199	0–2198
iPhone 17 Pro Max landscape	2208×1650	2208×1110	0–1109
iPhone 17 Pro Max portrait	1032×4212	1032×2370	0–2369

Verification

• In that run, each device gave the same mismatch in all 5 attempts, so the actual image is stable.
• The new heights match the rows of the old baselines that had content, and the top parts differ by 0.007 % to 0.48 %. The exception is iPhone 14 Pro landscape (5.7 %): its old baseline started in the middle of the cards, and the new image starts at the top of the element.
• I looked at each new image: the section from its top, no black or empty area, the ignored titles at the same places. In landscape on iPhone 14 Pro and 15 Pro Max, the iOS home indicator is over the bottom of the page, so it is also in the image.
• The other cloud jobs of that run passed (Android web, desktop web, OCR, Sauce Labs apps).

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: bc6869d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR