Nested and generic type resolving

I will go trough changes file by file:

TextEditorResolverProvider:
Before this change LookupSimpleNameOrType was always called with new List() so there was no way to resolve generic types. What I did here is some kind of hack because always passing "int" as generic type. I tested this on various combinations like nested multiple types Dic>>...
What is cool about this solution is very backward compatible and does not require any API changes to pass generic types or need to resolve them.
@mkrueger Looking for your thoughts about this.

CorObjectAdaptor:
Here are 2 changes:

Before it was caching name which was something like "Dictionary`2" so resolving Dic and after that Dic would result in wrong resolving in second case because it would return cacged Dic...
if (t.FullName.Replace ('+', '.') == name) replacing '+' with '.' because Csharp type resolver is resolving nested classes with SomeClass.NestedClass and not SomeClass+NestedClass so type is not found... Why don't we make resolver resolve with +? I tried hardcoing this to see what happens... new CsharpParser("...") don't like seeing "+" in middle of expression and starts treating it as AddOperation... @jstedfast same problem is with SoftDebugger seems like runtime expects '+'... One new test is failing now have some idea how to solve?
Rest of files are just tests and adding TypeResolve mock method
This pull is dependent on mono/debugger-libs#26 and vice-versa so bump is required.