Release version 1.3.1

Closes #109
Allow records to be created when offline and no store exists

This bug was introduced in #94 and v1.3.1.
Switch from Jasmine to Mocha + Sinon + Chai-bdd-expect

See #73, https://github.com/nilbus/Backbone.dualStorage/pull/73#issuecomment-44101373

- Rename integration_spec to acceptance_spec.
- Convert acceptance specs to mocha.
- Use an alternate idAttribute in all examples.
- Going forward, all features will be tested using Models and Collections.
- Moved legacy unit tests to jasmine/ for later conversion.
Mark acceptance tests as "legacy"

...because I want to refit them into this structure:

- Basic persistance
  - fetch
    - option: add
    - option: merge
  - save
    - create
    - update
    - updated attributes in server response
      - fetch
      - create
      - update
  - destroy
- Model and Collection interaction
  - Fetch collection, then fetch update model
- Override modes
  - mode
    - local
    - remote
  - override via
    - attribute
    - method
    - options
- Offline caching
  - Collection.syncDirtyAndDestroyed
    - Collection.syncDirty
    - Collection.syncDestroyed
  - Collection.dirtyModels
  - Collection.destroyedModelIds
  - fetch is local when there are dirty/destroyed
  - Temporary id for created models until synced
- Offline detection
  - Backbone.DualStorage.offlineStatusCodes
    - array
    - function
- Callbacks
  - options.dirty set when offline
  - When offline
    - no local store: error
    - with local store: success
  - When online
    - error code: error
    - 200 code: success
  - Delivery
    - success/error callback
    - $.Deferred
- Pre-parsing
  - Modellection.parse
  - Modellection.parseBeforeLocalSave
- Modellection.storeName
Implement acceptance tests for basic persistence
Implement more acceptance tests

Fix ineffective falsy expectation.
Invoke Callbacks when model with temp id is destroyed

When a model with a temp id is destroyed, then the success and error
callbacks should be invoked too.
Model with temp id should not be marked as destroyed

If a model with a temp id is destroyed, it should not be marked as
destroyed. Because it has never been synced with the server.
Use hasTempId instead of knowing what a tempId is
Merge branch 'destroy-tempid'

Closes #115
Update changelog for #115
Merge branch 'master' into mocha
Convert the spec from #115 to an acceptance style spec
Test mode overrides
Remove an unused deferred
Test offline status code override
Test Backbone.DualStorage.offlineStatusCodes as a method returning a success code

This failing spec reveals a bug that will be fixed in the next commit.
Allow Backbone.DualStorage.offlineStatusCodes to include 200 OK as an offline status

- Rename error callback parameter to xhr, since that is really what it is
- Update the mock ajax callback xhr argument to always include the http status and response
Allow Backbone.DualStorage.offlineStatusCodes to include 200 OK as an offline status

- Rename error callback parameter to xhr, since that is really what it is
- Update the mock ajax callback xhr argument to always include the http status and response
Rename offlineStatusCodes parameter to xhr in the README

This makes it clear that the xhr object is always passed, not the response body.

Also add this option to the changelog.