Fix full identity preservation backup/restore in Svelte Components

[NiKrause]

At the moment, "full identity and hash preservation" can only be demonstrated in Node.js demos using demo scripts (see examples). The same process also works inside the browser with the StorachaTest.svelte component in Svelte, but unfortunately the data is not loading from db after successful restore.

OrbitDB requests the same Manifest CID from the IPFS block storage but cannot locate the restored block (even though it was restored previously). It then queries the IPFS network for it, which fails with the error: "All promises rejected."

This functionality is essential in cases where the entire browser network (Alice, Bob, Peter, etc.) loses all of its data, and someone needs to restore the database one-to-one, including the original Manifest (database address), exact Identity (e.g., DID), and Access Controller (which could be IPFSAccessController, OrbitDBAccessController, or CustomAccessController).

An implemented alternative is to restore the IPFS blocks by analyzing their contents and adding them to a newly created OrbitDB instance using db.put(..restored block data).

An interesting test would be, when a backup was made through the browser code (StorachaTest.svelte), if it could be restored by the NodeJS code example.

[NiKrause]

Preparing a test:

1. Create a backup with simple-todo-app with a working UCAN-Delegation (full db & full hash preservation)
2. User restore-demo from orbitdb-storacha-bridge to restore the space into a db (full db & hash preservation)

[NiKrause]

Using example/restore-demo.js does restore from a Storacha space which was uploaded from simple-todo succesfully but cannot open the db from it's original address. Same issue as when doing it in a browser.

Now, the interesting question is: What breaks the data loading, after successfully restore.

We add more node tests:

1. Create OrbitDB, open db, add todos, backup, drop db, restore db into same OrbitDB instance - ok?
2. Same as 1. But with a new OrbitDB instance with exact same identity as when created

[NiKrause]

When running the demo.js with two different identities for backup and restore, data loading doesn't work after successful restore. Adding both identy and identities as parameter when doing a createOrbitDB doesn't help fixing it.

This means! I can only restore and load the data when I am not adding a new identity.