Log exceptions with FilePath & LineNumber

In PSES we use these extra properties when we log exceptions which gives us an awesome sense for where problems occurred:

https://github.com/PowerShell/PowerShellEditorServices/blob/ce265d7ed1e58db348b91c8a16679faa0aed0f0d/src/PowerShellEditorServices/Logging/LoggerExtensions.cs#L18-L20

If lsp could also add these properties to when it logs stacktraces, I think it'd give us a better sense for what went wrong when something does go sidewise like this very sad stacktrace I still need to debug 😅:

2020-03-11 01:34:15.665 -07:00 [FTL] Failed to handle notification textDocument/formatting
System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.PowerShell.EditorServices.Handlers.DocumentFormattingHandler.<Handle>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at OmniSharp.Extensions.LanguageServer.Server.Pipelines.ResolveCommandPipeline`2.<Handle>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at MediatR.Pipeline.RequestPostProcessorBehavior`2.<Handle>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at MediatR.Pipeline.RequestPreProcessorBehavior`2.<Handle>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1.<RouteRequest>d__6.MoveNext()

Start with the referenced PowerShell Editor Services Logging/LoggerExtensions.cs lines 18-20, then locate where this repository logs LSP exception stack traces. Determine how FilePath and LineNumber should be added to those logs; done means stack traces include both properties for relevant exceptions.