Add guide about content addressing data sets

[2color]

Describe your changes

This is a new comparison guide of UnixFS, iroh collections, and DASL/MASL for content addressing directories of files, covering overhead, determinism, subsetting, and ecosystem support.

After spending a lot of time comparing the three for a different use case, I thought it would be useful to share these insights, and embrace the plurality of the IPFS ecosystem.

Checklist before merging

• Passing all required checks (The beta Check Markdown links for modified files check is not required)

[github-actions]

🚀 Build Preview on IPFS ready

• 🔎 Commit: bc9a9fb
• 🔏 CID bafybeic24fg3tzxrjw7nem2qk3nkujurib6vbr2hc2wxucsp6v72oiwrby
• 📦 Preview:

  • dweb.link

  • inbrowser.link

[2color]

• Add more references to other pages like the lifecycle
• add a whole opening section about the more abstract notion of a Merkle proof with link to protoschool. Use analogy of club bouncer who has the root hash and each person who has proof of name with real world ID, and the Merkle path to the root.

[bumblefudge]

Suggested change

	- **Bundle mode** (`resources`): maps file paths to resource CIDs with per-file metadata — essentially a directory representation
	- **Bundle mode** (`resources`): maps file paths to resource CIDs with per-file metadata — essentially a logical unit representation, i.e. all the paths on a given domain apex (including nested ones)

not exactly a directory, can contain many directories included nested ones or none. more like a map of [pathed] relrefs to resources.

[2color]

I edited it. See the latest version

[bumblefudge]

modulo tweaks