This PR is an MVP version to address web view not tappable issue on iOS 26 (#175099). This issue cannot be fixed with pointer_interceptor, so if your issue can be fixed by it, it would be a different issue.

This PR performance a naive hit test that decides to block platform view gestures if the touch falls within the "overlap" region between Flutter widgets and platform view. This is not a complete solution since there are a few drawback:

1. There can be use cases where even if we touch outside of "overlap" (or no overlap at all), we still want to block gestures.
2. overlaps are merged into a single UIView in our current implementation. This means if you have multiple overlaps, the blocking region would be a bounding box that contains all overlaps.

To address the above drawbacks, a complete solution would require accessing Flutter's gesture arena, which will take longer time.

List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.

Part of #175099

If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
• I signed the CLA.
• I listed at least one issue that this PR fixes in the description above.
• I updated/added relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or this PR is test-exempt.
• I followed the breaking change policy and added Data Driven Fixes where supported.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.