Description of Change

Fixes #50783.

This PR regularizes bounds and constraints handling on Windows so that windows are created at their exact expected sizes and can grow and shrink to exact max/min constraints. Previously sizes be off by 8-16px because insets weren't always accounted for on creation or after various lifecycle events.

Bound/inset logic is fragile and hard to reason about, so I added about a dozen cross-platform constraint tests which run for both framed and frameless windows to help prevent regressions.

As was the case on Linux, the underlying issues originate in Chromium, which does not experience them as severely since it usually only enforces minimum sizes and it rarely changes bounds or constraints programmatically. The solution requires two Chromium patches:

1. A new patch which accounts for insets when clamping bounds to size constraints in DesktopWindowTreeHostWin::AdjustedContentBounds.
2. An update to an earlier patch from @CezaryKulakowski (fix: aspect ratio when max width/height is set #29101) which now corrects for insets when setting the aspect ratio.
   (This patch needs to use lower level DWM code since it does not have access to the frame.)

I was able to upstream the relevant patches when working on this problem for Linux, and I'll also attempt to upstream both of my changes as well as the previous work from @CezaryKulakowski.

Checklist

• I have built and tested this change
• I have filled out the PR description
• I have reviewed and verified the changes
• npm test passes
• tests are changed or added
• relevant API documentation, tutorials, and examples are updated and follow the documentation style guide
• 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 on Windows where windows appeared smaller than their configured size or were unable to be resized to their maximum size constraints.