Additional tests for text asset autosave

These should cover all the cases brainstormed at
https://github.com/PitonFoundation/atlas/issues/848#issuecomment-26346487

Addresses #848
Trigger autosave on keyup and initialize form less often

Trigger text asset autosave on keyup events instead of the editor's
blur event.  This is needed because the editor wouldn't always lose
focus when we needed to autosave, such as when switching sections.
So, listen to keyup events on the editor element and pass them
through to the underlying textarea, which in turn triggers the
change event on the Backbone Form view, which we bind to with the
autosave logic.

In the process of implementing this, I found that we were calling
``SectionAssetEditView.initializeForm()`` all over the place.
This was problematic because one place where the form was initialized
was on the model's ``change`` event. Since we're autosaving the model,
the form would get clobbered each time the model autosaves. In general,
it's not great to have the overhead of recreating and re-rendering
the view when it's not needed.

As far as I can tell, it only needs to be called when we're ready
to edit the asset. So, I removed all the calls and added one to
``EditState.enter()``.

Addresses #848
Cleanup autosave event  binding

* s/preventDelayedSave/cancelAutosave/
* Factor event handler for ``body:change`` form event into
  ``SectionAssetEditView.autosave()``

Addresses #848
Clean up text asset autosave tests

Eliminate some of the boilerplate, bootstrapping tasks.
Make test text distinct for each test to make it easier to keep
track of where one is when stepping through the tests and to make
it easier to run tests in succession.

Addresses #848