Generate constructor in derived type

Fixes #5274

Generate method test

Remove public scripting APIs that are not ready for release

Generate constructor had a logic bug causing it to consider any single constructor
in an abstract base class to be an acceptable base-class-constructor for it to
delegate to.  This was the case, regardless of what the actual parameter types of
that constructor were.  Now we actually consider the parameter types in this case
and only allow delegation if the parameter types would be assignable.

Fix issue where comments on a Collapse '#end region' tag were not being classified properly.

Fixes #3291

This was happening because the editor was asking us specifically about the span after what
was collapsed.  Due to a small logic bug (where we compared a PP-Directive's Span instead
of FullSpan), we didn't even bother diving into the comment to classify it.

Add comment to response file for interactive - fixes internal bug 99219

Disable CTRL+SHIFT+V in interactive window

Work around issue with ISymUnmanagedConstant.GetSignature...

Remove NuGetPackageResolver implementation

Provide a better exception message.  Fixes #4613

This method seems to be returning E_NOTIMPL in some cases.  When that
happens, the decoded type of the local will be ErrorType.  We should
drop these locals so that we can still Emit.

only try to smart-indent a constructor initializer if there's actually a constructor initializer

Fix a few issues related to trivia generation for add/remove suppression fixes from the error list. Unit tests have been added for the same.

LambdaReturnInferenceCacheComparer should treat Dynamic and Object as different types.

Improved warning for missing analyzer dependencies

By design, dependencies of analyzers must be specified explicitly to ensure that builds are consistent. However, this is surprising and the warning that is generated when a dependency is missing does not give any hints as to how the problem might be solved. I updated the warning to clearly explain what must be done to resolve it.

Old warning: "Analyzer assembly '{0}' depends on '{1}' but it was not found. Analyzers may not run correctly."
New warning: "Analyzer assembly '{0}' depends on '{1}' but it was not found. Analyzers may not run correctly unless the missing assembly is added as an analyzer reference as well."

Fixes #4057

Disable Ctrl+F12 in Interactive for now...

Update netci.groovy regex expressions.

Ignore constant expressions in CapturedVariableRewriter

Consider the current culture when copying xml doc comments in shadow copy provider.