Define the loose/minimal IPFS definition

[BigLep]

Done Criteria

There is public specs document with a name that articulates clearly what the minimal core definition of IPFS is. (I'll call this "avocado pit" for the rest of the issue.)

Why Important

As was most recently seen in n0's communication about a new direction for Iroh, we can have confusion around how an implementation can still be part of the IPFS big tent without having full compatibility with another implementation like Kubo. We want implementations to be able to easily say they're keeping compatibility with "avacado pit" even if they're breaking away from the "Kubo enchilada". This shouldn't raise alarm bells, and was a key thing motivated during IPFS Thing 2022.

Notes

1. "What is IPFS?" is a topic that has come up multiple times before. This spec is about getting to the core, that cases a big tent that empowers growing the IPFS pie from what the current implementations satisfy today. Related documents around this subject:
   • https://www.notion.so/Defining-IPFS-and-IPFS-integrations-1fc599790aa1424889c47d968e2db9d1?pvs=4
   • https://ecosystem-wg.notion.site/What-is-IPFS-Definitions-02d37b91f6824bba8c246fdcd5021a5c
   • https://pl-strflt.notion.site/A-Call-for-IPFS-Implementations-ae285080aaf24e4fbb5fee096605df68

[BigLep]

Fixed by #390