Hey! 👋 This PR...

• Changes console.log() to log directly to stdout/err, regardless of whether the --verbose flag is set
• Uses Node's util.inspect() function to stringify values as opposed to JSON.stringify()
• Logs to the console even if an inspector is connected
• Closes [feature request] console output #52 and 🐛 BUG: Regression with console.log-ing objects workers-sdk#3591

The end result is easier-to-read, detailed, coloured logs when running workerd locally. As an example, with the following script:

export default {
  async fetch(request, env, ctx) {
    console.log({ a: { b: 2 }, c: "x".repeat(50) });
    console.log(request.headers);
    console.log(new Map([["a", 1], ["b", 2], ["c", 3]]));
    console.log(new Set([1, 2, 3]));
    return new Response();
  }
}

Before:

After:

Follow-up tasks:

• Adopt util.inspect() from Node.js: the current polyfill has a few limitations. We should be able to implement the required native code to get around these.
• Switch to util.formatWithOptions() for formatting: this will add support printf-style % strings, as required for console.log()
• Export util.inspect(): if our util.inspect() function matches Node's, we should be able to export it from the node:util module if nodejs_compat is enabled.
• Custom inspects: some built-in classes have internal state that would be good to log. For example, logging request.headers above should probably log something similar to the Map.
• Unhandled exception logging: unhandled JavaScript exceptions should probably be logged in a similar way, and should definitely include the stack trace if we've got one.