Provide means to locate errors in type definitions

Following on from a few Types not having toString, equals and hashCode that should have I think we need to improve the tooling/model for this repo. 

The simplest option here would be to add a tool to spot differences. Overall though it might be a good idea to refactor some of the reflection support used in apex-ls so that we can create and validate TypeDeclarations directly. 