fix(material/core): sanity checks not disabled for node-based test environments

In #23374 we expanded the logic that checks for test environments to cover Jest and Mocha. The problem is that we were checking against the `window` which won't work in a Node environment, because the global variables are attached to the `global` object, not the `window`, even though there may be a fake `window` declared by the test tooling.

These changes resolve the issue by first checking against `global` before falling back to `window`.

Fixes #23365.

Author: crisbeto

src/cdk/platform/features/test-environment.ts

@@ -17,7 +17,17 @@ declare interface TestGlobals {
   Mocha: unknown;
 }
 
-const testGlobals = (typeof window !== 'undefined' ? window : {}) as {} as TestGlobals;
+let testGlobals: TestGlobals;
+
+// We check the Node-specific `global` first, because tools tend to add a fake
+// `window` in Node environments which won't actually receive global variables.
+if (typeof global !== 'undefined') {
+  testGlobals = global as {} as TestGlobals;
+} else if (typeof window !== 'undefined') {
+  testGlobals = window as {} as TestGlobals;
+} else {
+  testGlobals = {} as TestGlobals;
+}
 
 /** Gets whether the code is currently running in a test environment. */
 export function _isTestEnvironment(): boolean {

tsconfig.json

@@ -21,7 +21,7 @@
     "strictBindCallApply": true,
     "target": "es2015",
     "lib": ["es5", "es2015", "dom"],
-    "types": ["jasmine"],
+    "types": ["jasmine", "node"],
     "baseUrl": ".",
     "paths": {
       "@angular/cdk": ["./src/cdk"],