Docstrings for ContactsResource
ContactsResource get_or_create() api method should save created contacts
ContactsResource.handle_get_or_create() should reply with a 'created' flag
Merge branch 'develop' into feature/issue-220-contactsresource-contact-model-changes-should-always-be-saved
Merge branch 'develop' into feature/issue-220-contactsresource-contact-model-changes-should-always-be-saved
Merge branch 'develop' into feature/issue-216-contactsresource-needs-docstrings-and-commenting
Merge branch 'feature/issue-225-contactsresource-update-and-save-methods-need-to-handle-group-fields' into feature/issue-216-contactsresource-needs-docstrings-and-commenting
Merge branch 'develop' into feature/issue-216-contactsresource-needs-docstrings-and-commenting
Merge branch 'develop' into feature/issue-220-contactsresource-contact-model-changes-should-always-be-saved

Conflicts:
	go/apps/jsbox/contacts.py
Merge branch 'develop' into feature/issue-216-contactsresource-needs-docstrings-and-commenting
Merge remote-tracking branch 'origin/feature/issue-220-contactsresource-contact-model-changes-should-always-be-saved' into feature/issue-216-contactsresource-needs-docstrings-and-commenting
Updated ContactsResourcs docstrings based on the recent changes
reRestructuredText cross references use single backticks, not double
pep8/pyflakes fixes. (Hodgestar)
ContactNotFoundError should subclass ContactError
Change ContactStore dependents to handle of ContactError execptions
SNAEventHandler.find_contact() does not need ContactStore to be guarded for ContactError, moved out of try-catch block
GoApplicationMixin.get_contact_for_message() should accept an optional create arg, allowing the contact to be created if it does not yet exist
Create a contact in SurveyApplication.consume_user_message() and .end_session() when retrieving the contact from a message if the contact does not yet exist
Refactoring to prevent the non-settable contact fields from being set; review fixes