`isBrowser` check erroneously passes for `electron-link` bundled `node` applications

[themadtitanmathos]

azure-devops-node-api version: 10.2.1

Issue Description

global.window gets set in electron-link bundled applications, but global.window.navigator won't exist because it isn't a browser app, it's a node app. This means the current isBrowser check isn't quite enough, and the WebApi constructor will fail while trying to set the userAgent by accessing an undefined window.navigator.userAgent. I think a simple fix would be to also check window.navigator exists when calculating isBrowser.

Expected behaviour

isBrowser should not be true for electron-link (or any electron bundled) node apps.

Actual behaviour

isBrowser is true for electron-link (or possibly other electron bundled) node apps.

[github-actions]

This issue has had no activity in 90 days. Please comment if it is not actually stale

[alexgilevich]

The issue is still relevant. There is a discussion that is relevant to this: electron/electron#2288

The latest recommendation up there is to use process.versions.hasOwnProperty('electron') in the main process. That's probably what should be done because navigator.userAgent is defined in the renderer so there will be no issues with it (although nobody should invoke API in the renderer).

CC @anatolybolshakov