deps: V8: cherry-pick 385aa80

[refack]

Fixes: #26694

Original commit message:

Correct removal of redundant moves

The logic for removing while iterating is non-standard and
a left over from a previous index based loop. This patch
replaces it with a standard erase based version.

This fixes a runtime crash with MSVC that invalidates the
iterator and then asserts. This also makes the code safe
in case the last move can be redundant.

Change-Id: Ie6990e0d65a3b83a4b7da3e2e89ed4e60a6cd215
Reviewed-on: https://chromium-review.googlesource.com/c/1488762
Reviewed-by: Ben Titzer <titzer@chromium.org>
Commit-Queue: Ben Titzer <titzer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#59868}

Refs: v8/v8@385aa80

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• commit message follows commit guidelines

[nodejs-github-bot]

@refack build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/2935/pipeline

[refack]

V8-CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/2172/
PR-CI: https://ci.nodejs.org/job/node-test-pull-request/21589/

/CC @nodejs/v8-update @nodejs/platform-windows, since this resolves a regression (and is a backport of a validated change from upstream), I'd like this to be considered for fast-tracking.
Please 👍 here if you concur.

[refack]

P.S. @hashseed do you know why this code path is only live in a debug build, and is it relevant for node debugging (i.e. can we just turn it off?)