vm: introduce vm.Context

[devsnek]

Fixes #855
Fixes #31658
Fixes #31808

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

[devsnek]

the vm.Context constructor could also have a globalProxy option which takes an object. Should it?

[devsnek]

@nodejs/vm the vm.Context constructor could also have a globalProxy option which takes an object, like createContext(globalProxy), except it doesn't do anything to the object. Should it?

[joyeecheung]

What's the reasoning behind deprecating vm.createContext()? It has been around since v0.3.1 and I am pretty sure it would require significant effort to runtime-deprecate this (if that's ever possible). If it's working fine, I don't see why it has to be deprecated?

[devsnek]

@joyeecheung it's only docs deprecated. I don't think it would ever be feasible to runtime deprecate it. The idea of this PR is to provide a new API which doesn't act as confusingly (and somewhat dangerously) as the current API, and encourage people to use it.

[devsnek]

I'm still wondering about a globalProxy argument for new vm.Context. It could be useful, but due to V8's extremely odd implementation of the global proxy, it's quite awkward to work with.

[BridgeAR]

This needs a rebase.

[Trott]

@nodejs/collaborators This needs reviews.