Using gake - making grunt cleaner by separating it into tasks

Making grunt cleaner by making the Gruntfile as simple as possible
Now you can define tasks by creating a new file with the .test.js(coffee) extension inside the grunt/tasks folder
You can set a configuration for a task by creating a new file inside the grunt/config folder,
those files are auto-mapped by "gake" to the grunt.config.data object, by convention the filename is the object key, and the path is the namespace
so the following path: /grunt/config/sails-linker/devJs will create the following add the ["sails-linker"]["devJs"] object to grunt.config.data

This is the first step towards making the `sails g task [task_name]` possible!