Added the includes for the bootstrapper

This was modified to return a string containing URI directly, instead of a URI object which didn't work in the javascript world.

Run the bootstrapper so we have access to the Windows API.

This file was completely rewritten. This is the file that node-gyp uses to generate the msbuild solution used in the actual building of the module.

I modified this file to make it pass eslint. Also there was a "hacky" integration with the automatically generated typescript so I removed as we won't need it.

Added nuget install. It's preinstall and not postinstall because it needs to run before yarn runs node-gyp on this module (yarn runs it automatically during yarn install).

This file specifies nuget dependencies.

We need to add support for Windows bootstraper (this is a separate thing from the push notifications). We need it because we have an unpackaged app and we need to let Windows know that we will be using some native APIs. These are the needed includes. They point to the nuget package containing the windows app sdk.

This was modified to return a string containing URI directly, instead of a URI object which didn't work in the javascript world. We would have done the conversion to the string immediately in js anyway so we aren't losing anything. I suspect this didn't work out of the box because the NodeRT's generated code and wrappers depend on some UWP (packaged apps) objects and apis.

We need to add support for Windows bootstraper (this is a separate thing from the push notifications). We need it because we have an unpackaged app and we need to let Windows know that we will be using some native APIs. In the packaged apps this would be specified in the app manifest and Windows would do it automatically (there's a way to specify this in the project settings so msbuild generates this boilerplate automatically but I couldn't get it to work with our solution, using node-gyp and electron). We bootstrap the runtime depending on the version of the sdk, using constants from Microsoft::WindowsAppSDK.

The bootstrap library is contained inside the Microsoft.WindowsAppSDK nuget package. Normally (when using Visual Studio) these files would be included using the .props and .target files specified in the .vcxproj file, but node-gyp doesn't support that so we have to do things manually. We add the .lib file to the linker's paths and copy the required .dll to the release directory so our module can find it.

These are needed for the various .winmd files needed. These files specify the machine-readable metadata that describes the Windows runtime APIs. The first two lines specify the paths for windows.winMD and platform.winMD, they were updated to support building on newer versions of windows and visual studio (nodert is a bit old). The Microsoft.Windows.PushNotifications.WinMD that is being used in nodert_generated.cpp is included in the Microsoft.WindowsAppSDK nuget package so that why we add the path for it here (this whole module was generated from this winmd file, but we need to add this include because NodeRT assumes that these files are available globally for UWP apps and not just in a nuget package).

Now that we are only running Nuget on Windows, do we still need file: here?

The package installation still "fails" (exit 1 in preinstall.sh) and is then skipped because it's an optionalDependency. To use "0.0.1" this package would need to be a workspace (added in the root package.json). But we can't have "optional workspace". If one of the workspaces fails the whole yarn install will fail

Should we exit 0 then?

The plan was for it to fail so on non-Windows builds it's not included as a dependency (because it's "optional") of the desktop app. I've tried to make a dummy node-gyp configuration for macOS builds so that it can be built on both platforms but didn't have much luck.
That would probably be a better solution but I'm not sure if we prefer to try and figure it out right now or maybe as a follow-up.

Thanks for explaining again!