* Store checksums as a first-class piece of data in our persistence layer.

* Include the format version in the persistence checksum.

* Move symbol tree over to the checksym approach.

* Update sql persistence service to use checksums.

* Update tests.

* Fix wrapper.

* Remove projects.

* Add tests with checksums.

* Add more tests.

* Add test.

* Add comments.

* Simplify.

* Simplify.

* Revert.

* Revert.

* Revert.

* Add comment.

* Add comment.

* Add comment.

* Rev the checksum.

* Add comment.

* Add comment.

* Add comment.

* Add comment.

* Simplify.

* merge

* rename

* No allow checksym creation

* Rename

* cache strings

* simplify

* Remove optional params

* Update src/Workspaces/Core/Portable/FindSymbols/SyntaxTree/SyntaxTreeIndex_Persistence.cs
Co-Authored-By: NAndrew Harper <aharper@breuer.com>

Update editor packages

Revert "Revert RestrictedIVTs in M.VS.LanguageServices.csproj"

Require exactly one export of IStreamingFindUsagesPresenter when used

Revert RestrictedIVTs in M.VS.LanguageServices.csproj

Merge master to release/dev16.3-preview1

Merge master to release/dev16.3-preview1

Extract the RDT implementation for Misc files and VS open file tracker

Merge master to release/dev16.3-preview1

Merge release/dev16.2-preview3 to master

Remove support for explicit `object` generic type constraints

See #36401

When doing inline rename on a named type (interface, enum, or class) show a checkbox to also rename the file.

The checkbox will always show if the kind supports file rename

The checkbox will be disabled if any of the following is true:
- The type is a partial type with multiple definition locations
- The type does not currently match the file name

Extend ISyntaxFactsService to add IsTypeDeclaration
Implement file rename as part of conflict resolution for inline rename. This will allow other features to do file rename that also use the conflict resolver, all they need to do is set the correct option.

Fully update the type inferrer and add tests for generate field

Merge master to release/dev16.3-preview1

(cherry picked from commit 0a39cf90)

Introduces optimizations in lowering for an indexer access of the form
receiver[a..b]. With the optimizations, the generation of intermediate
System.Index and System.Range types will be avoided.

* Dont try and check tuple conversions in error cases:
- When checking an identity converison, also check for a bound tuple if the type isn't a tuple as we might have a bound tuple with an error type
- When checking a tuple conversion, don't GenerateConversion in the error case as we don't have a target type to generate against
- Update tests

The feature requires no extra work, just some tests.

Closes https://github.com/dotnet/roslyn/issues/30323

Merge master to release/dev16.3-preview1

Update 'Use pattern matching' to recognize other null checks

Code actions to configure severity and IDE code style options with .editorconfig