Error stack trace isn't preserved on rethrowing

[vyacheslav-sozap]

Description

Runtime: JavaScript. If you catch error (with try/catch) and throw it again, message in log will point to the place of rethrowing, not the original error throwing place. That breaks the error tracing a lot.

Steps to Reproduce

Build and run Nakama with following TypeScript module code:

let TEST_RPC: nkruntime.RpcFunction = function (ctx: nkruntime.Context, logger: nkruntime.Logger, nk: nkruntime.Nakama, payload: string): string {
	try {
		throw new Error('test_error');
	} catch (e) {
		throw e;
	}
}

let InitModule: nkruntime.InitModule = function (
    ctx: nkruntime.Context,
    logger: nkruntime.Logger,
    nk: nkruntime.Nakama,
    initializer: nkruntime.Initializer
) {
    initializer.registerRpc('TEST_RPC', TEST_RPC);
}

Expected Result

Error message in log points at line "throw new Error('test_error');"

Actual Result

Error message in log points at line "throw e;"

Your Environment

• Nakama: 3.10.0
• Database: PostgreSQL from Docker image postgres:14.1-alpine
• Environment name and version: Docker image heroiclabs/nakama:3.10.0
• Operating System and version: WSL2 on Windows 10

[sesposito]

This is a limitation of the JS engine we use and it cannot be changed at the moment, but we’ll see if it can be improved in the future.

Related to #801