fix: use macrotask state boundary in thread statequeue (#2116)

I initially thought a microtask boundary was sufficient, but with wasm
breakpoints with no symbols (where we resume synchronously) I observed
that sometimes the queued `resume` would not be dequeued before the
next paused event was handled. So this moves it to a full macrotask.

Author: connor4312

src/adapter/threads.ts

@@ -145,9 +145,10 @@ class StateQueue {
 
   public async enqueue<T>(operation: string, fn: () => Promise<T>) {
     // If we would no-op the task because it's already ongoing, make sure we flush
-    // microtasks first to avoid a race https://github.com/microsoft/vscode/issues/204581
+    // tasks first to avoid a race https://github.com/microsoft/vscode/issues/204581
+    // This initially flushed microtasks, but that wasn't always sufficient.
     if (this.queue?.operation === operation) {
-      await new Promise<void>(r => queueMicrotask(r));
+      await new Promise<void>(r => setTimeout(r));
     }
 
     if (!this.queue || this.queue.operation !== operation) {