node: Update p2panda to new API

[jsparber]

No description provided.

[mycognosist]

Here's an issue @sandreae and I found while testing this together:

• We moved the patch into the workspace root Cargo.toml and then tested Reflection
  • Initial sync and updates work for a new doc
  • Then one peer exits the doc (back to the main screen) and opens it again
  • No connection ever occurs...
  • We think this might have something to do with some state not being dropped
  • We believe that the network should be torn down when you leave a doc, and recreated when you join one
  • This behaviour does not occur on the current Flatpak version of Reflection

Any ideas, @jsparber ?

[jsparber]

• We believe that the network should be torn down when you leave a doc, and recreated when you join one

Could make sense even though it might make entering a document slower. Anyhow, this doesn't seam relevant here.

[adzialocha]

Any ideas, @jsparber ?

I could reproduce the issue in a test in p2panda-net, it might be related to the the topic being prematurely dropped by the node which stayed online. I'll investigate!

Edit: Yes, can confirm. I'm creating an issue here p2panda/p2panda#967

[jsparber]

Blocked on the p2panda release, but ready from my side.