Incidentally, fixes an acceptance test (which would have caught this
bug) not running. Its step regex was "They are correctly selected
after I reload the page$", which happens to be matched by "I reload
the page$", another step definition. Lettuce seems to arbitrarily pick
between definitions if they both match a step, so it's good to ensure
that each step isn't a sub-regexes of another.

to cms settings (it was throwing 500s for Stanford when the CMS
calls render_from_lms)

A new modulestore backed by mongo that changes the data format to
facilitate easy versioning, sharing content between courses, and fast
lookup of course structure and Scope.settings data.

Conflicts:
	cms/djangoapps/contentstore/tests/test_contentstore.py

So, changed handlers to look for either value.

including allowing javascript to serialize date/time natively.

Update existing tests and provide new ones to test new paradigm.

fix test to use the new create_item method rather than clone_item, which has been deprecated, and thus breaking the test

add a default XML serialization if the 'data' field is empty or None. Some XModules now - like video XModule - do not have XML set in the 'data' field

add a new django-admin command to dump out a course structure document. This is response to an emergency request from Harvard researchers.

Add boilerplate option to ItemFactory
Minor start date fix to not use microsecs

The defaults used to be rerandomize=always, showanswer=closed. This is
preserved for capa problems being imported from XML. However, for
courses, and for problems created in Studio, the default has been
changed to never/finished, to match the previous defaults used by
Studio.

Instead, we use XModule field default values when creating an empty
XModule. Driven by this use case, we also allow for XModules to be
created in memory without being persisted to the database at all. This
necessitates a change to the Modulestore api, replacing clone_item with
create_draft and save_xmodule.

This standardizes the XModule field default values to be the same as the
values that are presented by studio when a component is added to a
course.

The changeTime event isn't fired when the user types in the field, but
only when clicking on the time in the dropdown. I'd consider this a
timepicker bug, but for now we can just listen to the user typing in
the field and update the value (and thus validate) like we do with
other field types.