Migrate remaining Backbone.View subclass to Marionette.View

Backbone 1.1+ no long binds the options passed in to views on the view
itself (like models). Marionette maintains this behavior, so all existing
views have been changed to subclass from Marionette.View.

Signed-off-by: Byron Ruth <b@devel.io>
Port remaining workflow views to JavaScript

Signed-off-by: Byron Ruth <b@devel.io>
Remove embedded query dialogs from QueryList view

Fix #475

Signed-off-by: Byron Ruth <b@devel.io>
Move context filers parsing into 'json' change handler

This ensures that no matter how the json attributes are set on the
context, the filters state is updated.

This fix restores the ability to update the session context with
and existing saved query.

Signed-off-by: Byron Ruth <b@devel.io>
Ensure the filter state is hidden on re-render

This prevents the case when a filter is updated and invalid and then
removed.

Signed-off-by: Byron Ruth <b@devel.io>
Fix context panel message based on current route

Signed-off-by: Byron Ruth <b@devel.io>
Force applied filters to be enabled

This prevents the case that an existing filter that is disabled gets
updated, but has no upstream effect since it's disabled. In addition,
the  attribute is stripped to prevent using and old attribute.

As noted in the comment, a better method for cleaning the attributes
prior to being applied should be implemented.

Signed-off-by: Byron Ruth <b@devel.io>
Refactor support for required filters

The implementation has changed to be more generic. The new configuration
option `filters.required` is an array of lookups, that is, objects
containing keys that can be used to match a filter. This is usually a
concept id, field id or both. The option `query.concepts.required` is
deprecated, but will remain until the 2.4 release.

The 'context:required' event has been deprecated in favor of using just
the 'context:invalid' event since it is more general and contains the same
information.

Signed-off-by: Byron Ruth <b@devel.io>