(#136) - Fix "Changes with conflicts are handled correctly" against CouchDB 2.0

Do not assume ordering of _changes in the test. CouchDB 2.0 does not currently handle ?conflicts=true when fetching _changes (COUCHDB-2518) so skip these assertions for now when testing against CouchDB master.