* Compiler Options in PDB fixups

* Use MetadataVisualizerOptions.NoHeapReferences

* Add doc back

Avoid localizing Empty.resx

* Emit Clone methods in abstract records as abstract

The clone method is designed to call the containing type's
constructor, but this can't be done when the containing type
is abstract. A reasonable alternative is to make the method
abstract.

Fixes #44890

* Add test for abstract record in the middle

Dogfood the new .NET analyzers NuGet package

* Added Error 8053

* Requested PR Changes

* Update StructsTests.cs

* Update src/Compilers/CSharp/Test/Semantic/Semantics/StructsTests.cs
Co-authored-by: NRikki Gibson <rikkigibson@gmail.com>
Co-authored-by: NRikki Gibson <rikkigibson@gmail.com>

Roslyn repo currently includes analyzer package references to sub-packages of FxCopAnalyzers package (Microsoft.CodeQuality.Analyzers and Microsoft.NetCore.Analyzers). Due to the high noise level for default enabled CA rules from these packages, we end up turning off majority of these rules for the repo in our ruleset files. This change switches the repo from FxCop analyzers package to .NET analyzers package (NOTE: we plan to ship the analyzer assemblies from this package in the .NET SDK soon). This helps us dogfood the experience from this new analyzer package, especially from the perspective of noise from default enabled analyzers, while also cleaning up our configuration files. Some more details below:

- The new package has the same set of CA rules, but the legacy ones are now disabled by default.
- There are a handful of rules which are enabled by default as IDE suggestions (Info severity): either as part of the triage of pre-existing CA rules OR recently added by the .NET runtime team.
- There are even fewer set of rules which are enabled by default as warnings – all of these have been added by the .NET runtime team, none of the pre-existing rules are enabled as warnings in this package.

The core dogfooding aspect would be:

1. Enabled by default rules:
   1. Analyzer exception diagnostics (AD0001): absolute must to fix or disable these rules by default in the package.
   2. Noise from false positives: It would be a higher priority issue if the false positives are from a rule which is enabled as a build warning, but we should fix even false positives from info rules. We may also want to consider bumping these rules to lower severity or disabling them by default.
   3. Rules which had to be turned off for specific projects, say test projects. We should re-triage such rules and consider if they should be disabled by default.

2. Disabled/Info rules which were escalated to Info/Warnings as we found these to be valuable and reliable: We can potentially re-triage each of these rules and consider if they are valuable enough to have its default severity/enabled state changed to benefit customers.

Add new information for portable pdbs to help reconstruct the same compilation if source is available. Added spec file with detailed description of design.

Implements #41395

Fixes #44789

Merge records feature into master

* Put record parameters in scope withing instance initializers

https://github.com/dotnet/csharplang/blob/master/meetings/2020/LDM-2020-06-01.md
Also fixes #44879.

* Follow-up on merge

* Share closure across initializers and the base call.

Rename new feature to 'remove confusing suppression'

The compiler now uses a reserved name for the clone method which only
records will generate. Some existing tests are interesting if we ever
allow user-generation of the clone method but cannot be run in the
current state. I've left them in, but marked them skipped.

Fix duplicate/inaccurate results in LSP GoToImpl

Ensure correct binder is used to bind constructor initializers for synthesized parameter-less and copy constructors in records. (#44910)

Fixes #44898.

Use MEF instead of direct construction

Add feature to remove confusing use of suppression operator

* Add reqired API for moving SBD analyzer OOP

* Add the missing lisense header

* Add another missing lisense header

* Simplify some wrapper types

* Restore all the delete & edit API, mark them as Obsolete. Add a callback interface

* Fix typo

* Obselete some more APIs

* Add a dispose API

* Obselete more wrapper

* Remove the unused wrapper

* Remove a unused method

Relevant LDM notes - https://github.com/dotnet/csharplang/blob/master/meetings/2020/LDM-2020-06-01.md

Embed generated source texts in the portable PDB:
- Allows stepping in etc. in the IDE as well as a dump debugging after compilation
- Consistent ordering of generated syntax trees.
- Unique hint names
- Restrict hint names to file path legal characters
- Add tests

Update src/Features/CSharp/Portable/RemoveUnnecessarySuppression/CSharpRemoveUnnecessarySuppressionCodeFixProvider.cs
Co-authored-by: NManish Vasani <mavasani@microsoft.com>