Allow additional parameters to be passed to Casper, these can then be accessed from Casper using the Casper cli module.

Allows named or anonymous parameters, but doesn't yet deal with both.  The following grunt config:

ghost: {
  dist: {
    src: ['test/casperjs/**/*.js'],
    options: {
      direct: true,
      printCommand: true,
      args: {
        foo: '7071'
      }
    }
  }
}

would run 'casperjs test/casperjs/frontend.js test --direct --foo=7071'

Within Casper you can get the value of foo with 'casper.echo(casper.cli.get("foo"));'  If args is an array, unnamed arguments will be passed in instead.  See http://casperjs.org/cli.html for more details on cli arguments.
Removed unnecessary string.

At least I think it's unnecessary?
Remove leftover var.
Simplifies code added in [3bd1eb0], allows mixed named and anonymous parameters.

To use, options.args should be an array: ['unnamed', '--foo=bar', 'another-unnamed']
Grunt config supports named params by default, with unnamed params also available.

Add a params object to ghost options, params will be sent through as key value pairs.  You can create an array on params.unNamed to also pass through an array of unnamed params.
Move var assignment
Replace missing test command.

Removed option for unnamed params, as it doesn't work with the 'casperjs test' command.  It does work with the plain 'casperjs' command.  Here's three commands that work (including slightly confusing folder name):

casperjs test test/casperjs/frontend.js --direct --port=7002
casperjs      test/casperjs/frontend.js --direct --port=7002
casperjs      test/casperjs/frontend.js --direct --port=7002 foo bar

And one command that doesn't:

casperjs test test/casperjs/frontend.js --direct --port=7002 foo bar

As named params are the more likely usage, I've removed the option for unnamed commands.
Merge pull request #1 from m-allanson/master

Allow extra params to be passed through to Casper