Manually exclude Blade files from calls to PHPCS

[mattstauffer]

Fixes #198

Issue introduced because of changes to how PHPCS handles the situation of all files being excluded (in PHPCS 3 it was silent, in PHPCS 4 it throws a DeepExitException).

This PR exits before calling PHPCS if the paths provided, once Blade files are filtered out, are empty.

[tonysm]

Looks good to me! We're essentially handling the case where individual files are passed via the --dirty flag, right? Since PHPCS would filter out Blade files, if all the changed files are Blade files, that would result in an empty path list, and V4 would fail when we run on empty paths... if I got it right.

[mattstauffer]

@tonysm in the origina lissue, they were passing duster lint resources/views/filename.blade.php to trigger the error. This definitely fixes that. But yah, I believe the actual case is that --dirty is the most likely circumstance that would get us here.

I can't actually figure out how to trigger the original issue using --dirty tbh. If I change just a view, and run lint --dirty, I get No dirty files found.

If i change a view and a PHP file, I get the linting on the PHP file, but it skips the view with no errors.

So the only way I could trigger the error they were dealing with was by specifically passing blade files/folders.

./vendor/bin/duster lint resources/views
# or
./vendor/bin/duster lint resources/views/filename.blade.php

[mattstauffer]

I suspect this might also fix #200 but haven't heard back from OP. I can't figure out a scenario in which those issues are being triggered, but if you're ok with it @tonysm I'm inclined for us to just release it and see.

[tonysm]

@mattstauffer let's give it a shot. Merging it.