We should add ExceededMemoryLimit to the expected error codes when the javascript heap limit triggers an OOM event. On master the error code we expect is different, but we didn't update the test for 8.0: When we hit oom when initializing the js engine, on master we would fail immediately and throw a JSInterpreterFailure, but on 8.0 we'd get to this check and throw ExceededMemoryLimit instead.

This ticket is just updating the test on both master and 8.0. On master we can hit this because the test can be run in the sharding_last_lts suite which involves 8.0 nodes.