Task Engine no longer uses the 'ecosystem_id' column as a link to maestro objects, rather uses the flexible 'options' column.

Additionally, extension modules now implement the update_status
function, for extension specific data updates as the task instance
progresses.  The new [[_DEBUG]] global variable will output the full
configuration of the active task instance.  Associated with Maestro
issue # 222.
Audited references to maestro tables and objects, and cleaned them up.  Cleaned up straggler uses of the ecosystem_id column on task_instance in favor of the 'options' column.

Cleaned up a few calls to add_task_instance passing a value for
ecosystem_id.