feat: return transformed code as a string, do not wrap in vm.Script

[SimenB]

Summary

Extracted from #9252. Since jest-runtime is the one injecting arguments into the module wrapper, it should also say which arguments those are. This makes @jest/transform less coupled to the module wrapper, and thus to Jest's use case. It's marked as a breaking change since it changes @jest/transform's interface, but it's not a breaking change for users of Jest.

Test plan

Added some tests

[SimenB]

We could ditch the wrapping in @jest/transform entirely, and instead do that in jest-runtime directly. It's a weird coupling anyways.

EDIT: Currently doing this, and it's way cleaner. Probably something I should have done when @jest/transform was split out from jest-runtime

[SimenB]

@thymikee I've moved the entire wrapping into jest-runtime, I think it turned out way cleaner. Now @jest/transform does not have to care about the wrapper at all, neither creating it nor passing the correct arguments to it. I've also made jest-environment not care about the wrapper, since it actually doesn't care. It just invokes the script passed to it and returns the result. I'm quite happy with how this turned out

[SimenB]

this was broken anyways - if we declared it and then removed it here, we would still inject it from jest-runtime

[thymikee]

Lovely

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.