Part 2 of task context refactoring

[scalvert]

This adds the ability to pass task options from the config through to the task, and have the task correctly pluck off the options. It also changes the overall structure of task options to better match those of eslint and others.

The new Config structure is:

type CheckupConfig = {
    plugins: string[];
    tasks: {
        [fullyQualifiedTaskName: string]: "on" | "off" | ["on" | "off", unknown];
    };
}

As seen above, a task config can contain either

• a string that denotes whether it's enabled or disabled ("on"/"off" respectively)
• a tuple of string and unknown, where the string denotes whether it's enabled or disabled ("on"/"off" respectively), and the unknown value is the options to be passed to the task.

The task will only parse the options it owns; it won't parse any other config values for any other tasks, thus limiting the reach tasks have into one another's configs.

Examples

An example of disabling a configured task would be:

{
  "plugins": ["checkup-plugin-ember"],
  "tasks": {
	"ember/ember-types": "off"
  }
}

An example of passing options to a configured task would be:

{
  "plugins": ["checkup-plugin-ember"],
  "tasks": {
	"ember/ember-types": ["on", { "check-mixins": true }]
  }
}

TODO:

• Update config loading to normalize plugin names to checkup-plugin-*, so that configs can eliminate the need to specify the fully qualified plugin name.
• Pass in plugin name to task, so it can use the fully qualified plugin name to look up it's config, eg. ember/ember-types, where ember is checkup-plugin-ember

[scalvert]

I'm going to roll those TODOs over into a separate PR, to keep the scope of the PRs small.