systeminformation thread not ending: move error handling from utils to app

[khassel]

This reverts #4155 because that didn't work when running under electron (process.on("exit",...) is not called).

This approach puts a try/catch around the start function in app.js and in utils.js the process.exit(1) calls are replaced with throw new Error("process.exit:1");. The error message process.exit:1 is not evaluated in app.js but needed in the tests.

The short delay is now implemented in the catch block so the systeminformation is displayed.

[KristjanESPERANTO]

Looks good! One additional thought: would it make sense to introduce a small dedicated error class (e.g. ConfigError) instead of matching on the "process.exit:1" message string? That might make the intent a bit clearer. No strong opinion though - could also just as well be a follow-up PR.

[KristjanESPERANTO]

What about adding a log line here, so unexpected errors don't get swallowed silently? Something like:

Suggested change

	const int32 = new Int32Array(new SharedArrayBuffer(4));
	// planned config exits already logged their message before throwing
	if (error?.message !== "process.exit:1") {
	Log.error("Unexpected error during startup:", error);
	}
	const int32 = new Int32Array(new SharedArrayBuffer(4));

Otherwise anything else that throws in start() (a broken require, httpServer.open() failing, …) just turns into exit(1) without a stack.