As discovered during the review of D2363, the LoadGlobalScriptFile and LoadGlobalScript calls do not require a catch following rP14496 anymore.
These PSERROR_Scripting cases are only thrown when very serious errors occur, that is when there is out-of-memory happening when creating a JS object or array,
or when a C++ author wanted to register a JS class more than once, or use one that doesn't exist.
In that case the error should not be caught and runtime continued like nothing of concern to the remaining code happened, but end the program.
Or if some C++ code doesnt rely on a JS class being registered, then it should itself catch this exception.
Notice that with current code, it is actually possible to have an XML page that loads JS scripting code that calls C++ code that triggers a C++ exception where the exception is caught in the XML parsing code,
i.e. C++ (catch) -> XML -> JS -> C++ (throw).
This will, with the current code, result in the exception caught, printed as LOGERROR then segfault.
With this patch applied, it will result in the exception being triggered and ended without subsequent error.