* Theming for dirty tabs

* Improve border for dirty tabs
1. Make it thinner
2. Add a setting to disable it
3. Use 4 colors (activeFocused, activeUnfocused, inactiveFocused, inactiveUnfocused)
4. Move part of logic

* Hot apply of setting `dirtyTabBorder`

* Rename the setting

* Add default dirty border for all themes

* 3 of the 4 colors should be derived from the one main color

* Rename `dirty` to `modified`

* Rename `modifiedActiveFocusedBorder` to `modifiedBorder`

* Add modified border color for built-in themes

* More contrast

* Applying style directly on element

* Changing only color

* Using full border

* Using existing div for border styling

* Add setting to telemetry

* Uncomment cleanup code

* tweak colors and descriptions

* 💄

* 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

This reverts commit e84a2290.

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

Standardizing syntax and discouraging use of `this` inside tests

Fixes #59757