This reverts the patch from https://github.com/electron/node/pull/100
which never got merged due to reasons outlined in https://github.com/libuv/libuv/pull/2313

* Adds new patches that backports https://github.com/libuv/libuv/pull/2459
  and https://github.com/libuv/libuv/pull/2460

Based on https://github.com/nodejs/node/issues/29460

* feat: add env variable to skip binary download on npm install

* docs: add "Skip binary download" section to install tutorial

* fix: correctly crash when there is no crashReporter

* test: correctly crash when there is crashReporter

* ci: only kill WOA processes if they are running

(cherry picked from commit 844752cd97c4b010f0467bbfdfe4940934945523)

* ci: actually kill leftover processes on WOA testing

(cherry picked from commit a76d2d8e53458447579b865febbfaef5b2921f94)

* docs: improve and add examples for clipboard

* address feedback from jkleinsc review

Applies https://chromium.googlesource.com/chromium/src.git/+/b7b305f3389017cc42e2cfac6e7a319f42d5bde3%5E%21/

* build: handle arm64 node headers

(cherry picked from commit ff1f224d)

* node.lib for arm64 needs to go to specific dir

* build: get all the release assets when looking for one to delete

yeah we totally have more than 30....

* Update upload-to-github.js

This is a speculative fix for a crash we are seeing in `menuDidClose`.  We
can't repro the crash but the traces have it happening in this method
and just by reading through the impl the only part that jumps out as
Might Crash is this `model_` call.  Other methods in the menu controller
check `model_` before using it so it probably makes sense to do that here
as well.

* ci: test on woa hardware

* ci: run tests on WOA hardware (#20031)

* ci: run tests on WOA hardware

* Temporarily disable test until #20008 is resolved

* deterministically run tests in sorted order

(cherry picked from commit bedc5f7d)

* Disable test on WOA until #20008 is resolved

* use request instead of blur to detect openExternal success

* use blur event on mac, sigh

* oh, right, still gotta open an actual url

* Try to track down GPUinfo failure

* Make function async

* Check exitCode

* Try to resolve bad exit code on GPUInfo test

* Add logging to figure out failures on BrowserWindow.moveTop()

* Revert "Add logging to figure out failures on BrowserWindow.moveTop()"

This reverts commit e21ace30dc24ab212e06693ce655b78b1691c3f1.

* Disable test until #20110 is resolved

* fix lint issue

* build: add WOA release to list of releases

* Add job count info for sudowoodo

* Add verification of all assets

* Fix linting and add logic to wait before printing out results

* fix: ensure that the node env is not bootstrapped before running inspector

* fix: ensure we wait for the inspect to disconnect

This re-orders our node clean up so that we free the environment before
the task runner is cleaned up as node uses the task runner during clean
up.  It also calls WaitForDisconnect() to ensure that inspector agents
are notified that the context is going down.

* chore: update spec to catch SIGABRT

Revert "fix: make sure that menu bar gets focus even when you click an item to focus it first (#19710)" (#20035)

This reverts commit 27b2747b.

* chore: bump chromium in DEPS to 76.0.3809.140

* chore: bump chromium in DEPS to 76.0.3809.141

* chore: bump chromium in DEPS to 76.0.3809.142

* chore: bump chromium in DEPS to 76.0.3809.143

* fix: honor cursor blink rate on macOS

* fix: honor cursor blink rate on Linux

* fix: honor cursor blink rate on Windows

* refactor: clean up os_win cursor blink logic

* remove unneeded include

On multi-monitor setups where the monitors are not all origined at 0 on
the Y coordinate (E.g. vertical stacked monitors) the maximize
calculation was incorrect as it assumed top was "0".  This instead
adjusts the math to calculate the correct top value.