fix: handle async nature of [NSWindow -toggleFullScreen]

[codebytere]

Description of Change

Closes #25426.
Closes #25427.

[NSWindow -toggleFullScreen] is an asynchronous operation, which means that it's possible to call it while a fullscreen transition is currently in process. As such, this can create weird behavior (incl. phantom windows and missing traffic lights) and so we want to queue up transitions until the previous ones have completed. We do this by tracking when fullscreen transitions begin and end, and scheduling those transitions to execute in order after any current transitions complete.

cc @MarshallOfSound @nornagon @zcbenz

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• PR title follows semantic commit guidelines
• 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 multiple calls to window.setFullScreen could cause problems.

[nornagon]

the docs don't mention anything about not calling this twice.

[nornagon]

I think we could write some tests for this!

e.g.:

requestFullScreen immediately followed by cancelFullScreen should produce the appropriate events and the window should ultimately end up not in fullscreen mode. request -> cancel -> request should end up in fullscreen mode and likewise generate the relevant events.

[codebytere]

Holding this for a bit to explore a few edge cases

[trop]

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

[trop]

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

[trop]

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

[trop]

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