Extend Linux CI Support

[Automated] Merge 'stabilization' into 'master'

Refactor Compilation to pull features from ParseOptions

Changes InteractiveWindow.vsct to use image monikers

Port e7dd6093 to stabilization branch

See #3165

Gracefully bail out on extension method rewrite within conditional access expressions

Fixes #2593

User scenario: User types a conditional access expression with a subsequent extension method invocation. For example, "a?.Method().ExtensionMethod()". Attempting to perform any simplification (cast simplification, simplify name) or refactorings (inline temporary) causes a exceptions in the simplification engine and all these IDE services are disabled for the project.

Issue description: We are not handling conditional access expressions, and hence member access or invocations with null "left of dot" nodes, in our expander. Additionally, performing extension method expansion (to a static method invocation with receiver replaced as the first argument to invocation) is non-trivial.

Fix description: This change makes a defensive fix by:
1. Guarding against null reference exceptions.
2. Bailing out on extension method rewrite within conditional access expressions.

Approved 6/4 by ML Shiproom.

Include ContentType into assembly qualified type name emitted for an attribute argument.

Report rude edit when a partially executed active statement is edited

Fix System.String[] sometimes printing in unit tests

Removes old image resource
Reorders sections in InteractiveWindow.vsct to match the schema

Include accessible private members from outer types in Intellisense [stabilization branch]

Port f9bd1d1f to stabilization branch

Conflicts:
	src/EditorFeatures/VisualBasicTest/Completion/CompletionProviders/SymbolCompletionProviderTests.vb

make formatting performance better

...

this performance improvement is particularly for devdiv bug # 1089540

this makes the file in the bug to be formatted in several seconds compared to several minutes on my machine.

there were several issues. each one fixed by

#1, use concurrency on gathering operations.
#2, don't use too much time to split work to chunks if that requires more work than actually formatting.
#3, don't blindly set beginning of a file as inseparable start point for certain formatting options.

...

but these don't actually address the most impactful root cause of this perf issues. which is perf issue of GetPrevious/GetNextToken API in compiler.
(#3244)

formatter internally uses GetDescendantTokens to get all tokens at once and cache them which takes less than 1 second for the entire file (2M bytes size) in the bug. and use the cache internally.

but certain part of formatter (Rule Provider) can't use that internal cache, so it has to use the GetPrevious/GetNextToken to move around tokens, which in this particular bug, takes more than 40 seconds on my machine. and that is not even for entire file. (less than 1/12 of tokens)

I opened a bug to compiler team, hopely so that we can get better perf on those APIs.

in this PR, I mitigated the issue either by making more things to run concurrently or by changing logic which requires those APIs.

Addresses DevDiv 1169511.

Changes InteractiveWindow.vsct to use image monikers
Removes old image resource
Reorders sections in InteractiveWindow.vsct to match the schema

Enable xaml project test

Fix ITypeSymbolExtensions.IsOrDerivedFromExceptionType to handle type parameters constrained on Exception type or its subtype. Fixes #3254 

Fix a NullReferenceException when setting diagnostic severity.

**Bug:** Fixes #3098.

**Customer Scenario**

1. Customer adds the NuGet package for Microsoft.AnalyzerPowerPack, System.Runtime.Analyzers, or System.Runtime.Interop.Analyzers (really, any package containing FxCop rules implemented as Roslyn analyzers).
2. In the Solution Explorer, the customer expands the References | Analyzers | Microsoft.AnalyzerPowerPack.Common node.
3. User right-clicks on CA2229 and selects "Set Rule Set Severity" | Error.
4. The effective severity of the rule changes to Error.
5. User right-clicks again and this time selects "Default" for the severity, intending to reset it to its default value.
6. The severity is not adjusted, and instead the following dialog pops up:

![image](https://cloud.githubusercontent.com/assets/235241/7825354/dbe7155e-03c0-11e5-819b-5beac1ffd2ad.png)

Note that VS does not crash, and after dismissing the dialog VS continues to function.

**Fix Description**
It is possible to have multiple `<Rule>` elements with the same ID in a
rule set file, so long as they specify the same Action. This is likely
to happen with former FxCop rules--you'll end up with one copy under the
"Microsoft.Analyzers.ManagedCodeAnalysis" analyzer (from FxCop) and one
under "Microsoft.AnalyzerPowerPack.CSharp" or similar (from a Roslyn-based
analyzer).

When the user selects one of these rules in Solution Explorer and sets
the severity to "Default" we need to find each rule with the matching
ID, and remove them all from the rule set file. However, we remove the
rules while we're in the middle of the enumeration, tripping up the
enumerator and leading to `NullReferenceException`s.

The fix is to first flatten the enumeration of items to be removed to a
list, and then remove them.

The first commit in this pull request implements the fix, the next two reorganize the code and add unit tests.

**Testing Done**
I added unit tests around the code in question, include one that fails without the fix.

I also ran through the scenario described above and validated that the rule set was updated as expected after I implemented the fix.

Replace public fields with properties in compiler API

Deal with solutions with circular project references in MSBuildWorkspace

Code Model: When setting the name of a CodeElement, ensure that its members are updated

Port PR #3237 to stabilization -- Catch exceptions when creating a stream for signing

Handle "Color color" from VB completion

Use undo transaction so razor docs don't have redundant undos

Remove tail recursion and enable cancellation

Do not cut short binding of “return” statement even if expression has syntax errors.

Check current language version for “Global” keyword only if it starts namespace name in namespace declaration.

Remove recursion in GetFirstToken and GetLastToken

Conflicts:
	src/EditorFeatures/VisualBasicTest/Completion/CompletionProviders/SymbolCompletionProviderTests.vb

Now that Mac and Linux are using the same version of Mono, we can extend
the Linux support to match that of Mac.