Better stack trace for module not found error

[tbontb-iaq]

Currently, for common errors, easy-to-locate stack information can be output, for example:

Exception in thread "main" ReferenceError: m is not defined
	at <js> func2(lib/func2.js:4:138)
	at <js> func1(lib/func1.js:3:70-76)
	at <js> default(index.js:3:69-75)
	at <js> :module:eval(main.mjs:3:47-57)
	at org.graalvm.polyglot.Context.eval(Context.java:402)
	at MainKt.main(Main.kt:14)
	at MainKt.main(Main.kt)

However, for module not found errors, the stack information of the exception is not so good at locating the error location:

Exception in thread "main" Error: Error reading: /path/to/lib/not-found.js
	at org.graalvm.polyglot.Context.eval(Context.java:402)
	at MainKt.main(Main.kt:14)
	at MainKt.main(Main.kt)

I wish it would output a more useful error message. In Node, the output is just like the following:

Error [ERR_MODULE_NOT_FOUND]:
Cannot find module '/path/to/lib/not-found.js'
imported from /path/to/lib/func2.js

[oubidar-Abderrahim]

Tracked internally on GR 51880

[woess]

Implemented in 2b7fefa.