feat: [ENG-36536] tokens ts and new architecture

[cesaroeduardo]

Jira: https://aziontech.atlassian.net/browse/ENG-36536

Summary

• Implements a new, market-aligned design-tokens architecture with white-label brand tokens and semantic tokens.
• Standardizes token consumption to be Tailwind-oriented, reducing onboarding/learning curve and making usage more consistent across products.
• Includes fixes to ensure downstream consumers can reliably use the updated tokens.

Problems & Solutions

• Problem: Existing token organization made it harder to scale, white-label, and onboard new contributors.
  Solution: Created new tokens following a market standard proposal, introducing brand (white-label) tokens and a clearer primitives/semantic separation.
• Problem: Token consumption varied across consumers, increasing cognitive load and the chance of inconsistent usage.
  Solution: Shifted semantics to be fully oriented for Tailwind usage, providing a predictable, standardized way to consume tokens.
• Problem: Architecture changes can break downstream integrations.
  Solution: Added consumption fixes to keep consumers stable while migrating to the new structure.

Changes Made

• Added new tokens following a market-aligned proposal:
  • Figma reference: https://www.figma.com/design/t97pXRs7xME3SJDs5iZ5RF/Global-Tokens?node-id=0-1
• Introduced white-label brand tokens to support brand theming and customization.
• Introduced semantic tokens designed for direct, consistent usage via Tailwind (reduced learning curve + standardized consumption patterns).
• Reworked token structure across primitives and semantics, plus build outputs to reflect the new organization.
• Applied fixes to improve token consumption and prevent regressions in downstream projects.

How to Test

1. Checkout in this branch
2. Run npm link
3. Checkout na branch test-theme-new-tokens in console-kit
4. Update tailwind.config.js following the token readme
5. Run npm link azion-theme --legacy-peer-deps
6. Access http://localhost:5173/playground to see the new tokens

Testing Checklist

• Consume tokens in site and validate the new tokens in dark and light themes.
• Consume tokens in console-kit and validate the new tokens in dark and light themes.
• Consume tokens in docs and validate the new tokens in dark and light themes.
• Confirm no conflicts (e.g., duplicated token names, unexpected overrides, incorrect CSS vars/Tailwind mapping) across integrations.