Fix some style choices causing JSHint warnings

[thethomaseffect]

This pull request should contain zero functional changes. If there are any then please comment and I'll amend it before merging. The main changes are as follows:

• For multiline var assignments and ternary expressions, place operators before new line instead of after. This is the style JSHint advocates and much more common among the JS community.
• Change some statements to multiline to make them more readable (311-314, 446-448).
• Added some explicit newline characters on help information instead of joining empty strings.

[rlidwka]

For multiline var assignments and ternary expressions, place operators before new line instead of after.

Bad idea. In case of var assignments, trailing comma is easy to miss, therefore prone to errors.

Do you see an error here?:

var self = this,
   option = new Option(flags, description)
   oname = option.name(),
   name = camelcase(oname);

And how about this one?:

var self = this
  , option = new Option(flags, description)
    oname = option.name()
  , name = camelcase(oname);

Multiline statements with leading operators don't have that kind of error, but leading operators are much more readable than trailing ones.

I could easily read this, because indentation + leading ternary shows code structure nicely:

    return cmd._name
       + (cmd._alias
         ? '|' + cmd._alias
         : '')
       + (cmd.options.length
         ? ' [options]'
         : '') + ' ' + args
       + (cmd.description()
         ? '\n   ' + cmd.description()
         : '')
       + '\n';
   }).join('\n').replace(/^/gm, '    ')

But this looks like a random mess of strings with a different indentation. I noticed ternary operators only after a while:

     return cmd._name + (cmd._alias ?
         '|' + cmd._alias :
         '') +
       (cmd.options.length ?
         ' [options]' :
         '') +
       ' ' +
       args + (cmd.description() ?
         '\n   ' + cmd.description() :
         '') +
       '\n';
   }).join('\n').replace(/^/gm, '    '),

Added some explicit newline characters on help information instead of joining empty strings

Joining empty strings is actually an attempt to make code look like the output. If you're using newline characters, spacing between lines in the code and in the output is different. So "-1" on that as well.

I could agree that i > 0 && (lastOpt = this.optionFor(args[i-1])); looks weird, but generally I'd just leave current code as is.

I'd say don't use JSHint, it has some less than sane defaults, and it can't really be configured. Instead, you can use ESLint, which you can configure as you like. And don't blindly follow linter tools (before you review each and every one config option) - it is almost always a bad idea.

[SomeKittens]

I'm with @rlidwka on comma-first.

[thethomaseffect]

Cool, I'll drop the changes to comma first code and the help text

[thethomaseffect]

Removed old commit and made a new one so history is cleaner. Let me know if there's still any issues.

[rlidwka]

Looks good to me.

[thethomaseffect]

Great, thanks for the review!

[SomeKittens]

+1 for clean commit logs. Thanks for standardizing the code a bit!