feat: Add support for --exclude-node-modules to subcommands.

[coreyfarrell]

This adds support for the --exclude-node-modules option/setting to
instrument, check-coverage and report sub-commands.

Add testing to verify that --exclude-node-modules=false is honored for
all commands.

[coveralls]

Coverage remained the same at 96.429% when pulling 8678cef on coreyfarrell:excludeNodeModules into 8da097e on istanbuljs:master.

[coveralls]

Coverage remained the same at 96.429% when pulling 8678cef on coreyfarrell:excludeNodeModules into 8da097e on istanbuljs:master.

[coveralls]

Coverage remained the same at 96.429% when pulling 8678cef on coreyfarrell:excludeNodeModules into 8da097e on istanbuljs:master.

[coveralls]

Coverage remained the same at 96.429% when pulling 8678cef on coreyfarrell:excludeNodeModules into 8da097e on istanbuljs:master.

[coveralls]

Coverage remained the same at 96.429% when pulling b0f29ff on coreyfarrell:excludeNodeModules into 8da097e on istanbuljs:master.

[bcoe]

I know this has been explained to me before, but refresh me on why this couldn't be handled by passing in alternate exclude rules that don't include node_modules.

Trust the research you've done on this topic, and am 👍 just curious.

[bcoe]

It's a little weird that this refactor happens in this pull, seems like an improvement to picking and choosing parameters though.

[coreyfarrell]

@JaKXz saw that I was manually adding yet another option to this constructor, asked if we could do this.

[coreyfarrell]

I know this has been explained to me before, but refresh me on why this couldn't be handled by passing in alternate exclude rules that don't include node_modules.

exclude rules are handled by test-exclude which adds **/node_modules/** to the exclude list if it's not there already, unless you add the excludeNodeModules: false option.