feat: log the fullMessage with more details about the error

[rigor789]

If there's a fullMessage on the passed in Error (this comes from NativeScriptException), log that to the console because it includes more info. For example, if a module fails to compile/parse - now we should see the line/column and the file name of the exact location that fails:

Before:

***** Fatal JavaScript exception - application has been terminated. *****
NativeScript encountered a fatal error: Uncaught SyntaxError: Invalid or unexpected token
 at 
	require(:1:232)
	at (file:///app/index.js:12:1)
	at require(:1:232)

After:

***** Fatal JavaScript exception - application has been terminated. *****
NativeScript encountered a fatal error:

Error calling module function
Cannot compile /Users/rigor789/Library/Developer/CoreSimulator/Devices/EFBBAB23-8AA7-4A85-87D7-A18A78A910FA/data/Containers/Bundle/Application/3F99A2A6-E454-48B9-ADAC-581D191A563C/TestRunner.app/app/test.js
SyntaxError: Invalid or unexpected token
File: (file:///app/test.js:2:17)

StackTrace: 
	require(:1:232)
	at (file:///app/index.js:12:1)
	at require(:1:232)


SyntaxError: Invalid or unexpected token
File: (<unknown>:1:231)

StackTrace: 
	require(:1:232)
	at (file:///app/index.js:12:1)
	at require(:1:232)

Note: the double StackTrace in this example is because these are multiple errors, one from LoadScript and one from LoadModule - the LoadScript one includes the line/col/filename to test.js:2:17 whereas the LoadModule error does not. We can further improve this down the line, since in this example, the 1st stack trace is all we really need... But extra info never hurts...