fix: unclickable regions in some draggable BrowserViews

[codebytere]

Description of Change

Closes #27131.
Closes #27149.

Fixes an issue where some BrowserViews might exhibit unclickable button behavior when loading some websites. What was happening was that #26738 made the mistaken assumption that snapped areas should be draggable, which meant that when users set -webkit-app-region: no-drag the areas would become draggable (and thus not clickable).

Tested with https://gist.github.com/f1426205af6799b5d208d1cd54136457 and confirmed not to regress initial fix made in #26738 with https://gist.github.com/7278c8c62ec976110afb47ef2d861a7a.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Fixed an issue where some draggable regions were not clickable when loaded into BrowserViews on Windows.

[release-clerk]

Release Notes Persisted

Fixed an issue where some draggable regions were not clickable when loaded into BrowserViews on Windows.

[trop]

I was unable to backport this PR to "10-x-y" cleanly;
you will need to perform this backport manually.

[trop]

I have automatically backported this PR to "12-x-y", please check out #27177

[trop]

I have automatically backported this PR to "11-x-y", please check out #27178

[quanglam2807]

Thank you so much, @codebytere!

My app relied quite a lot on BrowserView so this bug is critical. Is it possible to cut a release with this patch this week?

[trop]

@codebytere has manually backported this PR to "10-x-y", please check out #27222