feat: Use websockets for sync-realtime

[kyscott18]

Description

Using websockets to replace the current polling algorithm would be more performant and cheaper.

ponder/packages/core/src/sync-realtime/index.ts

Lines 810 to 855 in afba4c3

	const enqueue = async () => {
	try {
	const block = await _eth_getBlockByNumber(args.requestQueue, {
	blockTag: "latest",
	});
	const latestBlock = getLatestUnfinalizedBlock();
	// We already saw and handled this block. No-op.
	if (latestBlock.hash === block.hash) {
	args.common.logger.trace({
	service: "realtime",
	msg: `Skipped processing '${args.network.name}' block ${hexToNumber(block.number)}, already synced`,
	});
	return;
	}
	const blockWithEventData = await fetchBlockEventData(block);
	consecutiveErrors = 0;
	return queue.add(blockWithEventData);
	} catch (_error) {
	if (isKilled) return;
	const error = _error as Error;
	args.common.logger.warn({
	service: "realtime",
	msg: `Failed to fetch latest '${args.network.name}' block`,
	error,
	});
	// After a certain number of attempts, emit a fatal error.
	if (++consecutiveErrors === ERROR_TIMEOUT.length) {
	args.common.logger.error({
	service: "realtime",
	msg: `Fatal error: Unable to fetch latest '${args.network.name}' block after ${ERROR_TIMEOUT.length} attempts.`,
	error,
	});
	args.onFatalError(error);
	}
	}
	};

Currently enqueue is used with setInterval, but should be swapped out with a websocket request, similar to https://viem.sh/docs/actions/public/watchBlocks

Other notes

This will require some updates to the rpc infrastructure to separate out websockets and https, and also be able to introspect as to whether a websocket transport is available