async_hooks: avoid extra frame copies in AsyncLocalStorage.run() - #67396

With the AsyncContextFrame implementation, every
AsyncLocalStorage.run() built two copies of the current frame: one to
enter the new value and another one in the finally block to put the
previous value back. Both copies went through the Map iterator
protocol, which calls next() and allocates an entry array per store.

Copy frames with forEach() instead, and when fn() neither replaced the
current frame (enterWith()) nor removed a store from it (disable()),
put back the frame that was current before run() instead of building
a new one. Otherwise keep building a new frame as before, so that
those changes stay visible after run() returns. getStore() now does a
single lookup unless the stored value is undefined.

A side effect is that after a top-level run() returns the current
frame is undefined again, as it was before run(), instead of a frame
that holds the previous value of the store. getStore() returns the
same values either way.

Measured locally:

  als.run(i, noop)                          100 ns ->  16 ns
  als.run(i, noop), two other stores set    145 ns ->  35 ns
  await als.run(i, async fn with 2 awaits)  250 ns ->  89 ns
  async_hooks/async-local-storage-run.js    7.0M  ->  20M ops/s

Assisted-by: claude:opus-5.5
Signed-off-by: Gürgün Dayıoğlu <hey@gurgun.day>