docs: update manifesto

[achingbrain]

Refs #35

• Removes permissions section as it's not relevant to general usage
• Updates out of date sections and adds links to relevant modules
• Adds emojis

[BigLep]

Hi Alex. I tried looking at this with fresh eyes and will someone not close to Helia get what Helia and why it exists.

It seems like another key design goal is to break open the "black box" of IPFS and have better visibility into what is happening by allowing a lot more events that can hook in to monitor and debug.

This probably doesn't belong here (maybe FAQ?) but I think we want to callout the things that arne't customizable. It sounds like the main area is data transfer currently, is that right? (We're assuming Bitswap and we don't expose configuration of bitswap - is that right?). (We have configurability over Content and Peer routing though as those are controlled by js-libp2p.

A laid visual could likely help here showing the relationship between the various components

• helia
• libp2p node
• datastore
• blockstore
• bitswap
• other helia modules
• user application (consumer of helia)
  I don't exactly know how the picture should look but it seems a bit surprising not to have any architecture diagrams anywhere in the repo. It will also be useful for those who are more visual in their understanding.
  (Understood visual is more work. That can be a separate item. I expect it will be useful for IPFS Thing presentation. Let me know if it would be helpful to whiteboard together.)

[BigLep]

Feel free to merge after you pick through the comments that make sense to apply now and backlog the others.