Show source location for native runtime errors

Runtime errors raised by native standard-library and desktop-control methods could appear in Studio with no useful source location. In the reported case from the forum, a desktop app crashed with Control has already been added to a window or container, but Studio surfaced the diagnostic at <unknown> and the out-of-process desktop run could also collapse the result to App exited with code 1.

Studio should report the ObjoBasic call site that triggered the native runtime error, so the error is clickable in the Errors panel and can show the containing member, such as Window1.Opened Line n.