* mark NFW from OOP critical

currently, whenever OOP throws an exception, we show infobar saying "restart VS". whenever that happens, we report NFW. now those NFW will be marked as critical and we will stop reporting NFW after that in VS.

basically making critical NFW behavior same as fatal watson in VS. and management will treat critical NFW same as fatal watson.

also, now we will show callstack like code fix exception when info bar is shown

* xml document fix

* fix build break.

* changed button to hyper-link to follow same pattern as other info bar (code fix)

show remote exception in callstack view.

* introduced enum for Watson Severity

* Revert "Revert "move StreamJsonRpc to 2.x from 1.3.x (#33960)" (#34654)"

This reverts commit 297aaf20.

* fix streamJsonRpc version conflict errors

* move stream json rpc to more recent version and remove unnecessary explicit dependency

* fix nuget version conflict issue

* json rpc array bug workaround

* move ToArray fix to lower layer

* underlying issue is fixed in stream json rpc already and inserted to VS before we going in.

removed workaround.

This reverts commit b6285348.

* move StreamJsonRpc to 2.0

* use object and collection initializer

* changed to throw rather than return

* share JsonRpc creation when it can share code

* add linked files to share code

* more moving around so that we can have linked file working

* addressed PR feedback

* changed name to WatsonReporter

* moved to latest streamjson version

* added a way for partner to add thier own json converter to roslyn service hub service base type

* fixed test break.

it is caused by behavior changes between StreamJsonRpc 1.x and 2.x

* added comment follow PR feedbacks

* updated comment following feedbacks

with set SERVICEHUBTRACELEVEL=All set, vs should put more logs in %temp%\servicehub\logs

while doing this, already found an issue where JsonRpc would throw bad RPC head exception. working with ilya to find out how that can happen.

moved cancellation to each InvokeAsync and use cancellation support provided by JsonRpc rather than cutting connections

let OOP to be killed

not always but in certain case where cancellation is raised in between 2 analyzers.

found issues here and there on its cancellation handling.

fixed 2 known OOP issues

1. there is a known issue where RequestServiceAsync might fail randomly.
   people are looking at the root cause, but until that is fixed,
   we will retry rather than failing right away.

2. if we close named pipe stream in the middle of object writer/reader is
   using them, we can get various exceptions. make sure we check cancellation
   before propagating that exception.

add try catch at the first await so that we can get dump at right exception point rather than having it as inner exception

I just JsonRpcClient internal as before. I remembered why I made this internal. I wanted to use this in unit test. still want to use it in unit test

added some comments and refactored some code.

This reverts commit 720f5c5e, reversing
changes made to 6a6043c3.

changes include
make SourceText::GetChecksum and AnalyzerTelemetry contructor public.

added MustRunInProc in IBuiltInAnalyzer and some clean up around serializing Solution/Project/DocumentId and how DocumentState is exposed.

simplified temporary storage service's temporary storage management and added ability to attach to existing temporary storage

solution checksum and serialization service.

added remote host client
- this gives an ability for host (vs) to talk to remote host (service hub)

rename and moving files between feature/workspace layers
- only real change is having ICompilerDiagnosticAnalyzer interface which can either have inproc implementation or out of proc implementation.
- inproc is needed since diagnostics are in feature layer and one who uses feature layer out side of VS host need an implementation.

added RemoteWorkspace
- RemoteWorkspace has host agnostic implementation of roslyn features/services/workspace that will run in remote host

added service hub component and setup project for service hub
- service hub component is basically thin layer that deals with converting data to pass in to RemoteWorkspace

made devdiv insertion tool to ignore servicehub related files

support byte and char array natively in ObjectReader/Writer

this gives an ability for host (vs) to talk to remote host (service hub)