ensure overridden effectors are invoked (though the "rich" detection done in EntityType for config-keys still should be applied),
and prefer effector definitions from statics over those from methods
display tasks better
be stricter about tags used to mark entity association from tasks (major) -
a big step towards moving away from tasks altogether as most usages now go through BrooklynTasks;
this gives us clarity about which entity is submitting, which is the context, and which is the target (for effectors)

this may have damaged task/entity gc -- there is one failing test i haven't been able to fix (and have marked disabled,
for now, so i could build, but we should fix it asap!) -- EntityExecutionManagerTest.testUnmanagedEntityCanBeGcedEvenIfPreviouslyTagged
port SoftwareProcess so it supports hierarchical tasks, and inspection of individual ssh commands
fix a cross-execution-context bug, and make logging/warnings much less verbose and more informative
attach "stream" tags to tasks (in BrooklynTasks), and update ScriptHelper and SshTask to use this
adds task streams to the REST API and to the GUI; also tidies up misc elements of GUI (including clicking on a task takes you directly to drill-down (no inline summary), and blocking details for tasks in details top section)