fix: window bounds not scaled from screen coordinates

[samuelmaddock]

Description of Change

fixed #25811

possibly related to #25420 #21777

On Windows, the will-resize and will-move events emit the pending bounds of the window. However, they're reported in screen coordinates which aren't scaled according to the display scale factor.

Here's a clip of a window being moved between a 4k and 1080p monitor which causes its scale factor to change. The width/height of newBounds remains the same with this fix.

(as an aside, there seems to be an unrelated rounding bug with the width/height of currentBounds you can also see)

2021-05-13_20-13-01.mp4

No tests are included as I'm not sure whether we have a way to test display scale changes.

Checklist

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

Release Notes

Notes: Fixed will-resize and will-move events not scaling the emitted newBounds rectangle to the appropriate Windows display scale factor.

[pavelserbajlo]

changes look good to me, amazing catch, Sam! 👏 👏

[release-clerk]

Release Notes Persisted

Fixed will-resize and will-move events not scaling the emitted newBounds rectangle to the appropriate Windows display scale factor.

[trop]

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

[trop]

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

[trop]

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