:lipstick: spec description
Support inline listeners

This extends the command registry to support listeners registered on
individual elements in addition to selectors. The analogy is inline
styles vs selector-based styles. I’m hoping this will be the foundation
of integrating cleanly with legacy commands registered via our
jQuery::command extension.
Integrate jQuery::on and ::trigger with command registry dispatch
:lipstick:
Force native event handler to be registered for activation commands

We use onWillDispatch internally to manage activation commands,
activating packages *before* the activation command starts dispatching.
This means we need to explicitly tell the command registry to subscribe
to the command in question.
Remove logging
:lipstick: spec
Upgrade keymap to fix simulated command dispatch for detached nodes
Forward preventDefault to original event
Remove unused __handledByCommandRegistry property
Add workspace commands via command registry again

Now that legacy jQuery command listeners are properly integrated with
the command registry, these commands can be moved back.
Merge pull request #3734 from atom/ns-commands-backward-compatibility

Make command registry backward compatible with jQuery::on and ::trigger
Add TextEditorElement and make TextEditorView a wrapper around it

This is the next step on converting all internal views to custom
elements instead of using SpacePen. The TextEditorElement instances
are associated with ::__spacePenView fields that are used for supporting
legacy access paths via atom.workspaceView.
Destroy model if TextEditorView is explicitly removed for compatibility
Assign attributes passed to TextEditorView constructor
Update settings-view to fix specs
Null guard ::element in TextEditorView::component synthetic property
Update wrap-guide to fix specs
Forward .abortKeyBinding() on CommandRegistry events to original event
Move editor commands to global command registry