Reorganise component tests

[KevinRansom]

In my never-ending quest to improve testing here, I have re-arranged the FSharp.Compiler.ComponentTests test suite somewhat.

I have:

1. Shrunk the namespaces so that the first 2/3's of the screen is taken up with exactly the same text for every test category.
2. Reduced the number of top level categories by merging them, where it made sense to.

I expect this to improve the experience of running tests in VS, and probably VSCode at least a little bit. If we decide this is a decent improvement we can consider expanding it to some of the other suites.

Here is a before and after of the VS TestExplorer for ComponentTests:

[T-Gro]

Which were the actions taken please?

As far as I can see:

• Find "Fsharp.Compiler.ComponentTests." replaceWith ""
• Find test method with . replaceWith test method with _ (since . causes a new node in test explorer, even when part of method name)
• Consistent casing (e.g. fsc -> Fsc)

Any other?

[T-Gro]

Why is "Conformance" not a separate node with the children beneath, is it because of namespace vs. module approach we use across the test suite?

[KevinRansom]

Which were the actions taken please?

As far as I can see:

• Find "Fsharp.Compiler.ComponentTests." replaceWith ""
• Find test method with . replaceWith test method with _ (since . causes a new node in test explorer, even when part of method name)
• Consistent casing (e.g. fsc -> Fsc)

Any other?

@T-Gro -- Plus moving some tests into other groups to compress them, and removing and refactoring a couple of small modules. Yes.

[KevinRansom]

Why is "Conformance" not a separate node with the children beneath, is it because of namespace vs. module approach we use across the test suite?

Yes it would be nice if the nodes could split on namespaces, but I believe the test hierarchy is:

Assembly
      Full namespace
             Typename
                    Common leading portion of namespace name
                                Full testcase namespace name