`vm.Script`'s `importModuleDynamically` should get a reference to the `context` used to run it

<!-- Thank you for suggesting an idea to make Node.js better. Please fill in as much of the template below as you're able. --> **Is your feature request related to a problem? Please describe.** When implementing `importModuleDynamically` you don't have access to what context the script is executed with, meaning you can't pass the correct context when constructing a `Module`. We're also missing the `filename` of the `Script`, so resolving to the specifier passed is also not straightforward since it can be changed by `.runIn*Context()` calls from what I passed in to the constructor. **Describe the solution you'd like** I think adding `context` and `filename` as accessible properties on the `Script` instance passed to the function should work fine - it would mirror what you get when using `SourceTextModule` where I have access to `context` and `identifier`. It could also be passed as a third argument to the function passed in `importModuleDynamically` if you don't wanna change the `Script` instance itself. **Describe alternatives you've considered** The [implementation](https://github.com/facebook/jest/blob/30e802036291f4c9c9fd4feef6faba485df54dd2/packages/jest-runtime/src/index.ts#L1128-L1134) I've gone with in the absence of such an API is to get the context again and re-use the filename passed in the constructor. This works since I also have control over how the script is executed, but that might not always be the case. Mirroring the capability of `SourceTextModule` would be nice, though - where in the context of the callback in `importModuleDynamically` there's enough information to know how to resolve the specifier being requested and in what context it should run.