test: drop now-empty remote runner (#35343)

* test: drop the now-empty remote runner from CI

* move fixtures to spec-main

* remove remote runner

* fix stuff

* remove global-paths hack

* move ts-smoke to spec/

* fix test after merge

* rename spec-main to spec

* no need to ignore spec/node_modules twice

* simplify spec-runner a little

* no need to hash pj/yl twice

* undo lint change to verify-mksnapshot.py

* excessive ..

* update electron_woa_testing.yml

* don't search for test-results-remote.xml

it is never produced now

spec/api-web-contents-view-spec.ts

@@ -0,0 +1,37 @@
+import { closeWindow } from './window-helpers';
+
+import { BaseWindow, WebContentsView } from 'electron/main';
+
+describe('WebContentsView', () => {
+  let w: BaseWindow;
+  afterEach(() => closeWindow(w as any).then(() => { w = null as unknown as BaseWindow; }));
+
+  it('can be used as content view', () => {
+    w = new BaseWindow({ show: false });
+    w.setContentView(new WebContentsView({}));
+  });
+
+  function triggerGCByAllocation () {
+    const arr = [];
+    for (let i = 0; i < 1000000; i++) {
+      arr.push([]);
+    }
+    return arr;
+  }
+
+  it('doesn\'t crash when GCed during allocation', (done) => {
+    // eslint-disable-next-line no-new
+    new WebContentsView({});
+    setTimeout(() => {
+      // NB. the crash we're testing for is the lack of a current `v8::Context`
+      // when emitting an event in WebContents's destructor. V8 is inconsistent
+      // about whether or not there's a current context during garbage
+      // collection, and it seems that `v8Util.requestGarbageCollectionForTesting`
+      // causes a GC in which there _is_ a current context, so the crash isn't
+      // triggered. Thus, we force a GC by other means: namely, by allocating a
+      // bunch of stuff.
+      triggerGCByAllocation();
+      done();
+    });
+  });
+});