* window.nonNativeFullscreen uses simpleFullScreen on macOS

* Handle edge-case where user edits prefs while in fullscreen and can never escape it.

* change 'nonNativeFullscreen' to 'nativeFullscreen' and invert the default value

* Prevent maximize button from going to native fullscreen if nativeFullscreen == false

* Fix focus getting lost after simpleFullScreen and encapsulate more of electron's api

* Fix missing whitespace for eslint

* 💄

* restart properly when setting changes

* Handle screen resolution changes when in SimpleFullscreen

* fix issues to be merged

#60565

fixing simple cases of any[]

In these cases, the programmer has explicitly indicated that the type should be nullable

* restructure menubar data to shrink cache

* remove old menu

* avoid storing common defaults for enabled, checked, and isNative

* remove old cache data for menubar/keybindings

* enable dynamic menu on linux/windows
workaround to fix #33457

* Address feedback

* other comment

Using a custom version of the node typings is causing a lot of pain while trying to upgrade our build to use `@types` instead of the `d.ts` files we have to maintain. I believe we primarily maintain our own version for two reason:

- Custom require function
- setTimeout and other timer functions return NodeJs.timer instead of a number

These can both be delt with, the first by using interface augmentation and the second by switching to use any types for timer. I believe that the pain of maintaining our own node `d.ts` outweighs the benefits here

This change switches us to use the standard @types/node package for our node typings

* initial reenablement of dynamic menus with cache

* stitching the cached menu and fallback

* remove unnecessary object

We compile using the alwaysStrict flag so these directives are not needed.

This part removes most of the remaining use strict directives that were not caught by part 1 and 2

We compile using the alwaysStrict flag so these directives are not needed

This part removes most `use strict` directives that are right after the file header

We compile using the alwaysStrict flag so these directives are not needed

We set alwaysStrict so this directive is not needed