VF# FSI Window improvement for runtime exception display

# [FSI Tool Window] Click on exception message

I propose a click on the absolute file path or clr identifer in the picture below brings the caret at the location in appropriate file if it exists.


If some of the logic to be able to achieve this can be brought to FCS, it will also help better uniformization in the eco system, although I'm not sure what is the status on this (some tools embedding FSI may have that feature already)

## Pros and Cons

Pros:
* richer experience in VS that applies to all FSI users
* helps with developer workflow in larger scripts, and loading debug assemblies (should be able to browse to these)
* may fit in same line of investments that will be taken by MS around FSI in future to make VS/F# more appealing to scientific / data science / all non developer communities

Cons:
* Cost of working on the VS code
* Maybe there is undergoing work already (merge some C# / F# Interactive Tool Window feature set in a new implementation?) and this kind of smaller effort would clash

## Extra information

Estimated cost (XS, S, M, L, XL, XXL): medium

Related suggestions:

Quoting [A Taste of F# Interactive, Don Syme 2006 blog post](https://blogs.msdn.microsoft.com/dsyme/2006/02/18/a-taste-of-f-interactive-in-visual-studio/)

> What's really striking is the combination of interactive visualization, Visual Studio, .NET programming and efficiently executing F# code (remember, .the floating point code is running as optimized native code, often close to C++ speed). We have a few things to add before this is complete: for example some form of intellisense in the interaction window. But this combination feels like it is bringing many things together nicely. (Aside: you can of course do interactive visualization when using F# Interactive from Emacs too 🙂 I'm not so sure about "vi" !!)

## Affidavit (please submit!)

Please tick this by placing a cross in the box:
* [x] This is not a question (e.g. like one you might ask on [stackoverflow](http://stackoverflow.com)) and I have searched stackoverflow for discussions of this issue
* [x] I have [searched both open and closed suggestions on this site](http://github.com/fsharp/fslang-suggestions/issues) and believe this is not a duplicate
* [x] This is not something which has obviously "already been decided" in previous versions of F#. If you're questioning a fundamental design decision that has obviously already been taken (e.g. "Make F# untyped") then please don't submit it.

Please tick all that apply:
* [x] This is not a breaking change to the F# language design
* [ ] I or my company would be willing to help implement and/or test this