[internal/release/3.1] Update dependencies from dnceng/internal/dotne…

…t-extensions

- Coherency Updates:
  - Microsoft.NETCore.App.Runtime.win-x64: from 3.1.26 to 3.1.26 (parent: Microsoft.Extensions.Logging)
  - Microsoft.NETCore.App.Runtime.win-x64: from 3.1.26 to 3.1.26 (parent: Microsoft.Extensions.Logging)
  - Microsoft.NETCore.App.Runtime.win-x64: from 3.1.26 to 3.1.26 (parent: Microsoft.Extensions.Logging)
  - Microsoft.NETCore.App.Runtime.win-x64: from 3.1.26 to 3.1.26 (parent: Microsoft.Extensions.Logging)
  - Microsoft.NETCore.App.Runtime.win-x64: from 3.1.26 to 3.1.26 (parent: Microsoft.Extensions.Logging)
  - Microsoft.NETCore.App.Internal: from 3.1.26-servicing.22261.2 to 3.1.26-servicing.22273.3 (parent: Microsoft.Extensions.Logging)
  - Microsoft.NETCore.App.Runtime.win-x64: from 3.1.26 to 3.1.26 (parent: Microsoft.Extensions.Logging)

[internal/release/3.1] Update dependencies from dnceng/internal/dotne…

…t-extensions

- Coherency Updates:
  - Microsoft.NETCore.App.Runtime.win-x64: from 3.1.25 to 3.1.25 (parent: Microsoft.Extensions.Logging)
  - Microsoft.NETCore.App.Runtime.win-x64: from 3.1.25 to 3.1.25 (parent: Microsoft.Extensions.Logging)
  - Microsoft.NETCore.App.Runtime.win-x64: from 3.1.25 to 3.1.25 (parent: Microsoft.Extensions.Logging)
  - Microsoft.NETCore.App.Runtime.win-x64: from 3.1.25 to 3.1.25 (parent: Microsoft.Extensions.Logging)
  - Microsoft.NETCore.App.Runtime.win-x64: from 3.1.25 to 3.1.25 (parent: Microsoft.Extensions.Logging)
  - Microsoft.Extensions.DependencyModel: from 3.1.25 to 3.1.25 (parent: Microsoft.Extensions.Logging)
  - Microsoft.NETCore.App.Internal: from 3.1.25-servicing.22218.1 to 3.1.25-servicing.22218.2 (parent: Microsoft.Extensions.Logging)
  - Microsoft.NETCore.App.Runtime.win-x64: from 3.1.25 to 3.1.25 (parent: Microsoft.Extensions.Logging)

Merged PR 22046: [internal/release/3.1] Update dependencies from dnce…

…ng/internal/dotnet-extensions

This pull request updates the following dependencies

[marker]: <> (Begin:Coherency Updates)
## Coherency Updates

The following updates ensure that dependencies with a *CoherentParentDependency*
attribute were produced in a build used as input to the parent dependency's build.
See [Dependency Description Format](https://github.com/dotnet/arcade/blob/master/Documentation/DependencyDescriptionFormat.md#dependency-description-overview)

[DependencyUpdate]: <> (Begin)

- **Coherency Updates**:
  - **Microsoft.NETCore.App.Runtime.win-x64**: from 3.1.24 to 3.1.24 (parent: Microsoft.Extensions.Logging)
  - **Microsoft.NETCore.App.Runtime.win-x64**: from 3.1.24 to 3.1.24 (parent: Microsoft.Extensions.Logging)
  - **Microsoft.NETCore.App.Runtime.win-x64**: from 3.1.24 to 3.1.24 (parent: Microsoft.Extensions.Logging)
  - **Microsoft.NETCore.App.Runtime.win-x64**: from 3.1.24 to 3.1.24 (parent: Microsoft.Extensions.Logging)
  - **Microsoft.NETCore.App.Runtime.win-x64**: from 3.1.24 to 3.1.24 (parent: Microsoft.Extensions.Logging)
  - **Microsoft.NETCore.App.Internal**: from 3.1.24-servicing.22164.10 to 3.1.24-servicing.22179.7 (parent: Microsoft.Extensions.Logging)
  - **Microsoft.NETCore.App.Runtime.win-x64**: from 3.1.24 to 3.1.24 (parent: Microsoft.Extensions.Logging)

[DependencyUpdate]: <> (End)

[marker]: <> (End:Coherency Updates)

[marker]: <> (Begin:9535ce9e-e77c-458c-58f2-08d98e7730ac)
## From https://dev.azure.com/dnceng/internal/_git/dotnet-extensions
- **Subscription**: 9535ce9e-e77c-458c-58f2-08d98e7730ac
- **Build**: 20220330.2
- **Date Produced**: March 30, 2022 9:28:00 AM UTC
- **Commit**: 8e0af0dbdd80016da26eab546c3f10e943cea1bc
- **Branch**: refs/heads/internal/release/3.1

[DependencyUpdate]: <> (Begin)

- **Updates**:
  - **Microsoft.AspNetCore.BenchmarkRunner.Sources**: [from 3.1.24-servicing.22164.6 to 3.1.24-servicing.22180.2][1]
  - **Microsoft.AspNetCore.Testing**: [from 3.1.24-servicing.22164.6 to 3.1.24-servicing.22180.2][1]
  - **Microsoft.Extensions.CommandLineUtils.Sources**: [from 3.1.24-servicing.22164.6 to 3.1.24-servicing.22180.2][1]
  - **Microsoft.Extensions.NonCapturingTimer.Sources**: [from 3.1.24-servicing.22164.6 to 3.1.24-servicing.22180.2][1]
  - **Microsoft.Extensions.HashCodeCombiner.Sources**: [from 3.1.24-servicing.22164.6 to 3.1.24-servicing.22180.2][1]
  - **Microsoft.Extensions.Logging**: [from 3.1.24 to 3.1.24][1]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 3.1.24 to 3.1.24][2]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 3.1.24 to 3.1.24][2]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 3.1.24 to 3.1.24][2]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 3.1.24 to 3.1.24][2]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 3.1.24 to 3.1.24][2]
  - **Microsoft.NETCore.App.Internal**: [from 3.1.24-servicing.22164.10 to 3.1.24-servicing.22179.7][2]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 3.1.24 to 3.1.24][2]

[1]: ...

Tease LogHub dependencies apart in VS4Mac. (dotnet#6209)

- The LSP client LogHub tech used to be tied to windows  due to how the LogHub bits were acquired. I moved that component to have a win/mac separate impl.
- There's now a shared "RazorLogHubTraceProvider" at the core VS.Editor layer (platform agnostic VS). Hopefully we get LogHub in VS4Mac eventually!

Part of dotnet#6038

Merged PR 21313: [internal/release/3.1] Update dependencies from dnce…

…ng/internal/dotnet-extensions

This pull request updates the following dependencies

[marker]: <> (Begin:Coherency Updates)
## Coherency Updates

The following updates ensure that dependencies with a *CoherentParentDependency*
attribute were produced in a build used as input to the parent dependency's build.
See [Dependency Description Format](https://github.com/dotnet/arcade/blob/master/Documentation/DependencyDescriptionFormat.md#dependency-description-overview)

[DependencyUpdate]: <> (Begin)

- **Coherency Updates**:
  - **Microsoft.NETCore.App.Runtime.win-x64**: from 3.1.23 to 3.1.23 (parent: Microsoft.Extensions.Logging)
  - **Microsoft.NETCore.App.Runtime.win-x64**: from 3.1.23 to 3.1.23 (parent: Microsoft.Extensions.Logging)
  - **Microsoft.NETCore.App.Runtime.win-x64**: from 3.1.23 to 3.1.23 (parent: Microsoft.Extensions.Logging)
  - **Microsoft.NETCore.App.Runtime.win-x64**: from 3.1.23 to 3.1.23 (parent: Microsoft.Extensions.Logging)
  - **Microsoft.NETCore.App.Runtime.win-x64**: from 3.1.23 to 3.1.23 (parent: Microsoft.Extensions.Logging)
  - **Microsoft.NETCore.App.Internal**: from 3.1.23-servicing.21608.5 to 3.1.23-servicing.22122.4 (parent: Microsoft.Extensions.Logging)
  - **Microsoft.NETCore.App.Runtime.win-x64**: from 3.1.23 to 3.1.23 (parent: Microsoft.Extensions.Logging)

[DependencyUpdate]: <> (End)

[marker]: <> (End:Coherency Updates)

[marker]: <> (Begin:9535ce9e-e77c-458c-58f2-08d98e7730ac)
## From https://dev.azure.com/dnceng/internal/_git/dotnet-extensions
- **Subscription**: 9535ce9e-e77c-458c-58f2-08d98e7730ac
- **Build**: 20220223.2
- **Date Produced**: February 23, 2022 5:39:56 PM UTC
- **Commit**: 8934ddbf6c4fbc697b8f63eb5a49fb21ccffc56b
- **Branch**: refs/heads/internal/release/3.1

[DependencyUpdate]: <> (Begin)

- **Updates**:
  - **Microsoft.AspNetCore.BenchmarkRunner.Sources**: [from 3.1.23-servicing.22101.1 to 3.1.23-servicing.22123.2][3]
  - **Microsoft.AspNetCore.Testing**: [from 3.1.23-servicing.22101.1 to 3.1.23-servicing.22123.2][3]
  - **Microsoft.Extensions.CommandLineUtils.Sources**: [from 3.1.23-servicing.22101.1 to 3.1.23-servicing.22123.2][3]
  - **Microsoft.Extensions.NonCapturingTimer.Sources**: [from 3.1.23-servicing.22101.1 to 3.1.23-servicing.22123.2][3]
  - **Microsoft.Extensions.HashCodeCombiner.Sources**: [from 3.1.23-servicing.22101.1 to 3.1.23-servicing.22123.2][3]
  - **Microsoft.Extensions.Logging**: [from 3.1.23 to 3.1.23][3]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 3.1.23 to 3.1.23][4]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 3.1.23 to 3.1.23][4]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 3.1.23 to 3.1.23][4]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 3.1.23 to 3.1.23][4]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 3.1.23 to 3.1.23][4]
  - **Microsoft.NETCore.App.Internal**: [from 3.1.23-servicing.21608.5 to 3.1.23-servicing.22122.4][4]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 3.1.23 to 3.1.23][4]

[3...

Merge pull request dotnet#5938 from dotnet-maestro-bot/merge/main-to-…

…main-vs-deps

[automated] Merge branch 'main' => 'main-vs-deps'

Merge pull request dotnet#5933 from dotnet-maestro-bot/merge/main-to-…

…main-vs-deps

[automated] Merge branch 'main' => 'main-vs-deps'

Fix stale project.razor.json's from breaking project state. (dotnet#5910

)

* Fix stale project.razor.json's from breaking project state.

- **Problem:** When users would copy their Razor projects they'd typically also copy the `project.razor.json` that came with that project. If the copied project was under the same solutions directory what would happen is our language server would detect that copied project, deserialize its `project.razor.json` and then depending on when file system watchers fire we could get into a state where the copied projects `project.razor.json` would say its project file path was `OriginalProject.csproj` instead of `CopiedProject.csproj` resulting in stale `project.razor.json` data (TagHelpers, documents, Razor configuration etc.) being used. Typically this meant any new changes to the project like adding a project reference, creating a .razor file etc. wouldn't be picked up and then users would be flooded with diagnostics about tags not being recognized even though they were there.
- **Solution:** Added a new `SerializationFilePath` entry to the `project.razor.json` so when we deserialize we can compare the serialization file path with where we actually deserialized the `project.razor.json` and fail if they don't match. This in turn resulted in us needing to rev the `project.razor.json` serialization format to ensure that we don't operate on older formats of `project.razor.json` which don't yet have the `SerializationFilePath`.
- **Implications of reving the serialization format:** Once 17.1 releases we wont be able to re-use users `project.razor.json`s that are already on disk and will need to wait for the `project.razor.json`'s to be recomputed. In practice we always re-compute them anyways BUT we'll have a slightly slower startup time on initial project open. Reving will also make it so VSCode's current release as of writing this commit wont be able to re-use VS's `project.razor.json`'s  and vice-versa; meaning that if VSCode thrashes for ownership of the project.razor.json VS will explode more catastrohpically (no project state) which actually should be a good thing becaues it'll let us detect the scenario quicker. Of course once we re-release VSCode with the new serialization format then they will both be able to operate on the same `project.razor.json`'s
- Since we had to provide additional information to the `project.razor.json` serialization lifecycle I had to do-away with `FullProjectSNapshotHandle` and the automatic JsonConverter transformation of `ProjectSnapshot` -> `FullProjectSnapshotHandle`. Gist: we had to provide "where" we were serializing the file which isn't accessible in the converter. To do this I created a new `ProjectRazorJson` class that mostly emulates the pre-existing snapshot handle but represents a more accurate version of the world for us. Should also make seraching for `project.razor.json` bits easier :)
- Because we now have a new `ProjectRazorJson` type I went through the projects and renamed variables, classes etc. to match the new convention.
- Added a new test and fixed pre-existing ones to work with the new world
- Updated our test project.razor.json's serialization format so they'd be usable.

Fixes dotnet#5907

* Address code review comments.

* Fixup tests.