Better Laravel Integration

This is part of #11. It is just a proof of concept and has some major flaws before one would want to merge this.

- Wrap all Resque jobs in our own wrapper so that we can "Turn on the Lights" for Laravel.
- Handle jobs with names like `Controller@method` and map that where it needs to go.
- It should maintain backward compatibility with looking at `perform` methods as well as using (and preferring) `fire` methods when no method is provided in the job string.
I guess this could cause issues if you had a constructor that expected params. It's this or force jobs to be static. Not sure what the best call is here. Laravel jobs (from the [docs](http://laravel.com/docs/queues)) are not static.