docs: add content describing diff between datahub and acryl datahub

[shirshanka]

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[maggiehays]

Totally agree that checkboxes would be bland here, but the current styling is pretty tough to read. At a glance, they look like previously-visited hyperlinks; it's also really hard to see in dark mode:

[maggiehays]

Also, while scrolling down, it's hard to keep the mental model of which color maps to which - by the time I got here, I couldn't easily synthesize which was DataHub vs. Acryl DataHub:

[maggiehays]

Can we work with the Design team to create some static images so we're not limited to markdown formatting?

[yoonhyejin]

Agree, it's somewhat hard to understand this comparsion intuitively. I don't think it would be too crazy to use markdown table with checkboxes, something like this ; https://datahubproject.io/docs/api/datahub-apis#datahub-api-comparison

If the design is too bland we can do something like the table on a acryl website ; https://www.acryldata.io/
Yet i'm not a big fan of static images becuase the text wouldn't be searchable.

[yoonhyejin]

Also, i think we wouldnt need "How to read this list" if we go with the checkboxes. @shirshanka let me know if you need help with this.

[shirshanka]

Addressed review comments. PTAL @yoonhyejin

[yoonhyejin]

Add some nitpick comments but overall looks great. I hope we can link out more doc contents with this table in the future :)