fix: make dev cmd consistent with deploy cmd

[thsig]

Fixes #388.

Don't return a singleton build task by default in the dev command. This makes the dev command's behavior more consistent with the deploy command in watch mode.

[drubin]

Thanks for this I think this might solve some of the issues.

But it appears the structure/code is still slightly different between dev/deploy. My understanding is that the code should be fairly similar if not exactly the same and shareable but it's not.

I don't fully understand why? Why can't abstract it away so that when we fix/change something we change it in one place?

We have had a few bugs recently about the differences between these 2 commands behaving differently and every time we patch the logic.

Is there a solution of wrapping this login in a shared function that could potentially solve this once and for all?

[thsig]

@drubin: True, the structure of dev vs deploy is still different in a couple of ways, mostly in that dev uses both the getTestTasks and getTasksForModule helpers to generate the task list in its handler and changeHandler, where deploy uses only getTasksForModule.

On the other hand, the test command only uses the getTestTasks handler, and the build command simply returns build tasks and doesn't use either of these helpers.

We could consolidate getTestTasks into getTasksForModule and add an includeTests param, but I thought it was clearer to have the commands mix and match them explicitly.

That said, getTasksForModule is a bad name, just couldn't think of anything better to describe its return value.