fix: make console.logs not hang vitest-pool-workers when using workflows (#8832)

This goes way beyond me, but I noticed that I didn't use `patchAndRunWithHandlerContext` in `createWorkflowEntrypointWrapper` but other entrypoints did it - that seems to fix it. However, I'm not really sure how does `ExecutionContext` relate to our custom `Console` mock. Probably the test runner uses `waitUntil` to write into the vitest's stdout?

Author: LuisDuarte1

.changeset/eleven-papayas-take.md

@@ -0,0 +1,5 @@
+---
+"@cloudflare/vitest-pool-workers": patch
+---
+
+Make vitest-pool-workers not hang when console.\* is used in a Workflow

fixtures/vitest-pool-workers-examples/workflows/src/index.ts

@@ -7,6 +7,7 @@ import {
 
 export class TestWorkflow extends WorkflowEntrypoint<Env> {
 async run(_event: Readonly<WorkflowEvent<unknown>>, step: WorkflowStep) {
+console.log("ola");
 return "test-workflow";
 }
 }

packages/vitest-pool-workers/src/worker/entrypoints.ts

@@ -543,7 +543,9 @@ export function createWorkflowEntrypointWrapper(entrypoint: string) {
 }
 const maybeFn = instance["run"];
 if (typeof maybeFn === "function") {
-return maybeFn.call(instance, ...args);
+return patchAndRunWithHandlerContext(this.ctx, () =>
+maybeFn.call(instance, ...args)
+);
 } else {
 const message = `Expected ${entrypoint} export of ${mainPath} to define a \`run()\` method, but got ${typeof maybeFn}`;
 throw new TypeError(message);