Upgrade vm2 package

Problem/Motivation

In 9.5.x, running yarn audit reports the following critical issue with vm2:

┌───────────────┬──────────────────────────────────────────────────────────────┐
│ critical      │ vm2 vulnerable to Sandbox Escape resulting in Remote Code    │
│               │ Execution on host                                            │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ vm2                                                          │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in    │ >=3.9.11                                                     │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ nightwatch                                                   │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ nightwatch > proxy-agent > pac-proxy-agent > pac-resolver >  │
│               │ degenerator > vm2                                            │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://www.npmjs.com/advisories/1084716                     │
└───────────────┴──────────────────────────────────────────────────────────────┘

This has been discussed with the security team and it has been determined this can be handled in public.

Steps to reproduce

Proposed resolution

Upgrade vm2 in yarn.lock.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet