fix: event propagation after exiting fullscreen on Windows

[codebytere]

Description of Change

Closes #33721.

Fixes an issue where Escape keyboard events would not be properly propagated to the parent window after entering fullscreen and then exiting it again on Windows.

This was happening as a result of calling SetHtmlApiFullscreen(false) prior to calling exclusive_access_manager_->fullscreen_controller()->ExitFullscreenModeForTab(source). This created a race condition, wherein some platforms like macOS would work correctly becuase by the time !exclusive_access_context->IsFullscreen() was called, it wouldn't yet be true on macOS, and NotifyTabExclusiveAccessLost would relenquish its hold on keyboard event handling. However, on Windows, !exclusive_access_context->IsFullscreen() would be true, and thus the controller would continue to eat Escape key events. Fix this by adjusting the call order.

Tested with https://gist.github.com/bc382eeeb368b70fbed1e177bcaacfde on multiple platforms.

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 Escape keyboard events would not be properly propagated to the parent window after entering fullscreen and then exiting it again on Windows.

[nornagon]

Notes say "on macOS", should they say "on Windows"?

[release-clerk]

Release Notes Persisted

Fixed an issue where Escape keyboard events would not be properly propagated to the parent window after entering fullscreen and then exiting it again on Windows.

[trop]

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

[trop]

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