Add support for directives that do not have a restrict defined

I came across an issue with the way that directives and their respective restrict property were found. Pretty much the naive regex being used would look for `directive(` and then `restrict`, but not dependent on that restrict being part of that actual directive. The side-effect from this is that you end up missing whatever the next directive with a require property is.

This becomes an issue if you have a directive that doesn't have a restrict defined, in my case this ended up being a sample piece of code written into a comment block. However, angular doesn't actual require the restrict property to be defined since it has a default value.

I ghetto-hacked together a naive parser that limits the scope for checking for a restrict to the actual directive. It's very much not optimized and I only added a basic test to make sure it is working.