[Miniflare 3] Remove unused handleQueue() function from entry worker

[mrbbot]

With #656, the Queues dispatcher is now implemented as part of the broker Durable Object. We no longer send message batches directly from Node.js, so can remove queue handling from the entry worker.

Note the magic proxy enqueues messages through queue producer bindings like regular workers, so never used this endpoint directly.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f4ecf45

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[petebacondarwin]

No changes to tests because this is never used and makes no externally measurable change to behaviour?

[mrbbot]

@petebacondarwin exactly, this code has been moved here: 👍

miniflare/packages/miniflare/src/workers/queues/broker.worker.ts

Lines 190 to 209 in d1f1ef7

	#dispatchBatch(workerName: string, batch: QueueMessage[]) {
	const bindingName =
	`${QueueBindings.SERVICE_WORKER_PREFIX}${workerName}` as const;
	const maybeService = this.env[bindingName];
	assert(
	maybeService !== undefined,
	`Expected ${bindingName} service binding`
	);
	const messages = batch.map(({ id, timestamp, body }) => {
	if (body.contentType === "v8") {
	return { id, timestamp, serializedBody: body.body };
	} else {
	return { id, timestamp, body: body.body };
	}
	});
	// @ts-expect-error `Fetcher#queue()` types haven't been updated for
	// `serializedBody` yet, and don't allow `number` for `timestamp`, even
	// though that's permitted at runtime
	return maybeService.queue(this.name, messages);
	}