now, it includes flag whether given solution is for primary workspace or not.

this should benefit perf on initial solution load

removed API in service hub that internally play with data (options) in workspace rather than solution snapshot.

now, like other features, analyzer uses snapshot of options rather than mutable one from Workspace.

eventually we should only use OptionSet snapshot embeded in solution rather than one in workspace.

This is a workaround for #18563. See #19042 for a follow-up task to remove
this workaround.

1. write logs as warning rather than error when connection is closed (basically operation cancelled)

2. build compilation concurrently for diagnostic analyzers.

let OOP to be killed

Adrian was reporting high LOH fragmentation in OOP process due to this. I did some experiment and lowered buffer size to 12K that seems keeping current synch perf similar to now but way lower buffer size.

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

latest version of JsonRpc supports custom JsonConverter which I added for these 4 types. Checksum, SolutionId, ProjectId, DocumentId

we can add more to AggregateJsonConverter for common roslyn types.

unit test added

Add Razor Language Service shim for accessing the remote client

Add Razor Remote Workspace shim for getting access to the solution in
the ServiceHub process. This relies on the same set of Roslyn services
being called by the client to initialize state in the remote process.

Add overloads to the 'remote' solution service to avoid a need for IVT in
in the Razor Remote Workspace shim. Checksum is internal to Workspace.

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

Move Remote features down to lower levels now that the RemoteHostClient is available from the Workspace layer.

The important part is that we don't create these services until they are needed.
We don't need complicated logic about later on disabling them.  The current logic
attempts to disable them when the same packages that loaded them, get unloaded.
But packages only get unloaded when VS is shutting down. And we don't need to
do complex work in that case as our entire environment is going away.

--

In other words, we had complexity around returning teh service to an 'unstarted'
state just so it could be started up later.  But it will never be the case that
we'll ever start the service up again as the only reason we moved it to 'unstarted'
was because VS was shutting down.

Add out of proc CodeLens processing