Add IPLD compliance checklist to the website

[RangerMauve]

• Read over existing notes from warpfork, make sure on the same page with terms
• Propose order of checklist
• Initial draft of checklist
• Revised draft of checklist
• Add to website
• Add status from existing implementations

[warpfork]

Having a little togetherthinking time with @RangerMauve this evening and we've shuffled around a new TOC/outline order that we feel a little happier with than the last draft doc I put together. It follows:

• Core
  • Data Model
  • Codecs
  • Blocks
    • Hashing
    • CIDs
    • Storage & Transport (Might put in lower priority section?)
    • Link Loading
• Universal Interface = Data Model + Lenses
  • (just) Data Model
  • various implementations ((allows programmer to pick different native memory layouts))
  • Lenses: ADLs
  • Lenses: Schemas
• Operations ((things that you do functionally, over the UniversalAPI))
  • Pathing & Traversal
  • Selectors
  • Patch
  • ((future: prettyprint? transforms? etc. don't include these today, but may be future headings.))

((many sections need to say "and this should implement the Universal Interface", possibly linking forward to pathing/traveral to explain what that literally means.))

((some checklist items are going to be critical for getting a full compliance score; we're also starting to find some things that might be recommendations but noncritical, e.g. in storage & transport, a line for "you have a storage system that can take a path on the host filesystem and DTRT with CAS" would be recommended but technically not critical.))

[BigLep]

2022-06-14 conversation: in progress work happening here: https://hackmd.io/-2cqxrOPSXWy5mZt-OQ1QQ