fix: WCO pressed background state updates

[codebytere]

Description of Change

Closes #34763.

When a window with WCO is restored after the minimize button is clicked, the button was left in the STATE_HOVERED state. This meant that when the user restored (unminimized) the window, the button was incorrectly left painted as though the user was still hovered over it, and could only fix this by once again hovering over the button and then moving off of it. This issue is fixed by ensuring that windows controls are reset when the window is restored, since the buttons could neither be pressed or hovered over as that is occurring by the nature of the event taking place.

Tested by adding:

titleBarStyle: 'hidden',
    titleBarOverlay: {
      color: '#2f3241',
      symbolColor: '#74b1be',
      height: 60
    }

to the BrowserWindow ctor options of the default Fiddle.

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 the minimize button with WCO enabled would incorrectly be highlighted in some cases.

[codebytere]

Looks like a valid test failure - i'm looking into it!

[codebytere]

@clavin @mlaurencin tests fixed!

[release-clerk]

Release Notes Persisted

Fixed an issue where the minimize button with WCO enabled would incorrectly be highlighted in some cases.

[trop]

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

[trop]

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

[trop]

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

[trop]

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