check for schema equivalence by sorting keys in both schemas

[codekiln]

In 0.7.1 we shifted from raising an error to logging a warning when the schema in the codebase did not match the one requested from the database. This is a good start, but the hash_equals method could be more forgiving; if the hashes don't match, it should load them as dictionaries and check for equivalence, since order doesn't matter in elasticsearch schemas.

[codekiln]

Ran into this today, just a reminder, the easiest way to see if the schema has actually changed when the json_md5 differs for index my_index_name is:

>>> json.loads(DEMIndexManager.get_active_index_version('my_index_name').json) == json.loads(DEMIndexManager.get_dem_index('my_index_name').get_index_hash_and_json()[1])

If the result is True, then the schemas have not changed (even if their json hash differs because of key sorting). If the result if False, then the schemas have changed.