WIP: AngularJS support - DON'T MERGE

[Iristyle]

• Entire Angular API space covered
  • Some new features require implementing to make this 100%

[Iristyle]

Don't pull this into your master branch until you've had a chance to look at some of the //TODO: items inside the files.

This works pretty good, but there are a number of things which would make this really shine:

• [ ] #21 - Adding a "return" type for constructors, static_properties, static_methods, instance_properties, and instance_methods. Pretty much all of the changes I made to CoffeeComplete Plus.sublime-settings become unnecessary if this feature exists. I filled in return types for everything, with the assumption that this feature already exists. One of many examples here
• [ ] #23 Type aliases or inherits - for instance, I duplicate both ngScope and angular.element mutliple times because I have no other choice. I also made changes to my type definitions assuming this was implemented as inherits - example
• [x] #31 / implemented in #32 - A way to alias the names that show up in the completion list. In a couple cases, angular extends an existing API during mocks, and I want to annotate those function calls with something like [ngMock] so you know that it's only available when writing tests - example
• [ ] #18 - You already know about constructor support.. this would help in a few cases as Angular has a slightly unusual syntax in a few spots, for instance with filters. You retrieve a filter like $filter('name') .. then to use it, you invoke it right away, like $filter('name')(input, args) For instance $filter constructor returns a special date filter with its own constructor
• [ ] #22 - Support for multiple custom type definitions. I don't really want to pollute your existing custom jQuery types. I may not even want to include jQuery support. I'd rather ship an angular file, and enable / disable various custom type definitions through config (optimally inside the sublime project file).

Thanks for such a great plugin -- looking forward to some of these improvements! I was going to try to hack at one of those features this weekend, but it took me so long to cruise through all the Angular docs and test everything out, that I ran out of time... sigh.