Consider swapping Goja with Sobek for Javascript Processor

The JavaScript Processor uses Goja, and you have these caveats in your docs.

The execution engine behind this processor provides full ECMAScript 5.1 support (including regex and strict mode). Most of the ECMAScript 6 spec is implemented but this is a work in progress.

Imports via require should work similarly to NodeJS, and access to the console is supported which will print via the Redpanda Connect logger. More caveats can be found on GitHub.

This processor is implemented using the github.com/dop251/goja library.

For these same reasons, the k6 team at Grafana recently forked Goja into Sobek, where they merged their long-outstanding PR for ES Module support. It also looks like they've been merging all other commits to Goja.

Given these advancements, and the deeper resources available at Grafana, it seems to me that it would be prudent to switch to Sobek.

Start with the JavaScript Processor and its current github.com/dop251/goja dependency, then compare Sobek's supported features and compatibility with the processor's documented behavior. Verify whether switching engines preserves the existing require, console, and ECMAScript behavior; done means the processor works with Sobek without retaining the documented Goja limitations.