Create a view like Call Hierarchy for Data Flow Analysis (aka Value Tracking)

[sharwell]

This view would be launched when a user selects a value declaration or reference as opposed to a method declaration or reference. It would then be populated using the new Data Flow Analysis functionality of Roslyn.

[sharwell]

Additional scenarios from #34566:

Scenarios:

1. If I change the value of this variable, what code in which methods will be impacted?
2. We hit a NullReferenceException due to some parameter or other variable being null. How could this have happened? Where and from which methods could this value have come from? (The value doesn't have to be null, could be any other constant value, but null is probably the most common case)

[mikadumont]

Proposal

1. Add a right-click menu option called View Value Origin along with a shortcut to View Value Origin

2. Entry point on members: property, field, local variable, captured variables, parameter, events

3. Right click on a member which will open the right click menu with the View Value Origin option:
   

4. The View Value Origin command will always be visible in the right click menu and if the user selects the View Value Origin menu option and their cursor isn’t on a member they will get a warning dialog.

5. Selecting View Value Origin will open the Value Origin Window. The member where you invoke View Value Origin will show up at the top highlighted and expanded by default. The following node will be closed by default. The Value Origin results window should show the file name, line number, class name, method name, and the value. The value should be bold.

[ryzngard]

@mikadumont marking this as closed with the release of value tracking. Future work or improvement should have a separate issue