refactor: glob by default for commands

[nfischer]

This PR accomplishes:

• globStart defaults to 1
• commands have argument globbing by default
• to opt out of globbing, use allowGlobbing: false

Commands have been refactored to take advantage of this new default value.

Also, this PR begins to store default values in a JS object for each wrapOption, which will probably make it easier to keep track of the defaults in the long run. Because this uses common.expand(), this will have a slight conflict with #490 (this is just because I renamed expand to objectAssign in that PR). I'll resolve the conflict after either PR is merged and update accordingly.

This might be a good time to discuss if we want wrapOutput to be true by default, since it seems like it'll be the norm for a command to use that option.

[ariporad]

I vote for this to default to true.

[nfischer]

This now also makes wrapOutput default to true, and refactors accordingly.

[nfischer]

Gonna give this an LGTM since it just covers the refactors discussed. @ariporad chime in if there are any other issues.

[nfischer]

The only difference, I suppose, is that this removes the exception thrown if pipeOnly and canReceivePipe conflict (since it didn't work as well when specifying default options). We can provide documentation instead saying that pipeOnly overrides canReceivePipe (which is probably also a reasonable behavior).

[gyandeeps]

Upgrade from 0.7.2 to 0.7.3 broke .test() function since it has allowGlobbing to true now.

• Was this intentional?
  • If yes, Why was this breaking change introduced with a minor/patch version?

[nfischer]

@gyandeeps thanks for pointing this out. It looks like the change in behavior was a mistake. I'll review this more carefully and revert any changes to behavior.