Add grunt task to promote pull requests when Fuel UX is a submodule or bower component

- Also add comments to serve tasks.
- Helps Fuel UX play nice within other projects, especially related Fuel UX projects, and allows running Fuel UX's grunt tests simultaneously.

**Contributing to Fuel UX when using Fuel UX from within another project:**

If `bower_components` folder is your parent project's .gitignore, then `git clone` your forked Fuel UX repository into the bower folder and git will treat it as it's own repository, but not be versioned within your project. Run `npm install` like normal. If your parent project's `.bowerrc` file is set to something besides `bower_components`, you may need manually move the bower files to `bower_components` within the `fuelux` folder.

Use `grunt servesubmodule` for testing Fuel UX simultaneously as you test your own project. This will run JavaScript tests and prevent livereload conflicts allowing you to continuously run test while modifying Fuel UX within your parent project. When you've added your feature to Fuel UX and have it working within your parent project, push to your fork and create a pull request into the upstream Fuel UX to contribute.
So the only different between `submodule` and `full` is that livereload is false.  I would suggest using grunt options on the command line for this instead of creating a new task. http://gruntjs.com/api/grunt.option