Modify jIO API to keep user data not modified.
    jIO.get({"_id": "foo"} -> jIO.get("foo")
    jIO.remove({"_id": "foo"} -> jIO.remove("foo")
    jIO.post({"title": "bar"}) -> jIO.post({"title": "bar"})
    jIO.put({"_id": "foo", "title": "bar"}) -> jIO.put("foo", {"title": "bar"})
    jIO.getAttachment({"_id": "foo", "_attachment": "enclosure"} -> jIO.get("foo", "enclosure")
    jIO.removeAttachment({"_id": "foo", "_attachment": "enclosure"} -> jIO.remove("foo", "enclosure")
    jIO.putAttachment({"_id": "foo", "_attachment": "enclosure", "_blob": blob} -> jIO.remove("foo", "enclosure", blob)

jIO.get does not return an _id attribute anymore.

Do not store data as encoded string but as data URL.
Set a default mime type for text attachment if not provided.

Allow to choose which action_reference will be used as default view.

openCursor only return one entry per index value by default.
Use IDBKeyRange to get the expected behaviour.

Simplify storage and tests code.

Change the database structure so that the "attachment" store contains one entry per attachment.

Add tests for memorystorage.
Drop copy/paste code in jio.post. Should be added in a standalone storage if needed.

All ERP5 callable can be represented as attachment.
Editing (FormData) is done with putAttachment.

It is not possible to directly create/modify.

Contrary to previous implementation, the content is not shared between all memory storages.

Allow to read all entries in localStorage.
localStorage becomes just one jio document with many attachments.