[DOCS] Docs describing the API, utilization and examples of the `@daffodil/design` package

[xelaint]

📄 Documentation Request

What were you doing?

Expected behavior

Docs Changes

• Getting Started (docs(design): update getting started docs #3271)
• Release Notes (Consider creating a "what's new/release notes" for @daffodil/design #3303)
• Tabs: Usage, API ([FEAT] Tabs Component #3123)
• Colors
• Typography
• [DOCS] Update daff-illuminate function documentation #1412
• [DOCS] @daffodil/design Theming Guide #2901
• Design Tokens
  • [FEAT] Design Tokens/CSS Custom Properties #1880
  • Add design tokens page and write documentation ([DOCS] Add documentation for design token/css custom properties #2801)
• @daffodil/design SCSS Documentation
  • SCSS API Reference ( Use SASS Parser to auto generate utilities docs #3405 )
  • SCSS Tutorials
    • [DOCS] "How to create a custom component" tutorial in @daffodil/design #3393
    • Write a guide on how to make your custom component handle dark and light mode.
• [FEAT] Display Example Viewer in Markdown Files #2903
• Move @daffodil/design component examples to its own @daffodil/design-examples package #1235
• Behaviors
  • Usage docs for design core behaviors #4388

Cleanup

• Deprecate and remove daff-illuminate. (Deprecate and remove the daff-illuminate function #3772)

Existing Documentation

Environment

Daffodil version: X.Y.Z
Angular version: X.Y.Z 

 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

[damienwebdev]

There are only 3 large ideas remaining in order to mark this as closed.

• The example viewer's visibility in daff.io and the supporting infra around that [FEAT] Display Example Viewer in Markdown Files #2903
• An overarching review of the design component docs - Per Component Docs Review #3771
• SCSS Utilities documentation - Use SASS Parser to auto generate utilities docs #3405