implement node:events in javascript

[paperclover]

Currently, node:events is implemented in C++, which may sound fast but ends up being much slower than a pure JS implementation as the rapid hopping between native code and JS with listener callbacks is a lot of overhead. This PR is not only porting the node.js events into JS as closely as possible, but also trying to get it as fast as possible.

Currently node.js own events implementation beats us, but we've gone from being 4x slower to something more like 2x.

Still debating which implementation details are best, such as

• Object vs Map: they lead to different gains in different tests
• An optimization where having only one listener is not an array but just the function itself. This seems to be slower than just having and looping over a length=1 array.

Also, setting real-world benchmarks that tests actual usage instead of than a single ".emit()". Microbenchmarks are handy but we need to consider the bigger picture.

required todo:

• Replace the C++ module out for events.exports.js
• Find the best implementations for addListener and emit
  • the array clone we have to do seems to be the slow part?
• EventEmitter#once (implemented but check if can be made faster)
  • optimization: compare arrow fn vs the current bind solution.
• EventEmitter#removeListener (reimplement)
• EventEmitter#prependListener
• EventEmitter#listenerCount
• EventEmitter#types
• EventEmitter.once (async iterator)
• EventEmitter.setMaxListeners
• EventEmitter.getEventListeners
• error event
• capturing rejections
• validators

things might not do in this PR

• Remove the C++ implementation, it's still in the code somewhere.
• EventEmitter.on (async iterator)
• EventEmitterAsyncResource

Fixes #2190

[github-actions]

✅ zig fmt errors have been resolved. Thank you.

^{#fe3260916318ebe8a9840666f3955bb23fc29162
zig v0.11.0-dev.2571+31738de28}

[paperclover]

3 opened issues for less important but missing features. passing all tests for everything else though

[Jarred-Sumner]

looks like there are unintentional changes to submodules

can you reset those?

[Jarred-Sumner]

nice

[Jarred-Sumner]

We can make Array and Object come from primordials here

Suggested change

	var { isPromise } = import.meta.primordials;
	var { isPromise, Array, Object } = import.meta.primordials;