Disable code_on_top_scope by default until the noise can be reduced (…

[rnelson0]

…#580)

[binford2k]

I dunno about this. It seems like throwing the baby out with the bathwater.

I can see the argument, though I'd wager that linting the site manifest is not a common usage, in comparison to linting modules. What if we accepted another command line argument, say --manifest or --site, that could enable/disable a set of tests to make it more appropriate for testing the site manifest.

For future enhancement, I'd like to add test groups that could do this in a more generic way.

[rnelson0]

It probably is throwing the baby out with the bathwater, in a way - however, it's not an existing check in a published gem version yet, so disabling it by default only means that users have to enable it if they want to use it.

Long term, group flags of some sort would definitely be helpful.