feat: respect OS or root class for dark mode

[bswags]

• Change account kit's tailwind to respect OS level or class name dark mode
• Have the demo app use the "light" classname to override the OS setting so that the toggle is always in control

Pull Request Checklist

• Did you add new tests and confirm existing tests pass? (yarn test)
• Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
• Do your commits follow the Conventional Commits standard?
• Does your PR title also follow the Conventional Commits standard?
• If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
• Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
• Did you follow the contribution guidelines?

---

PR-Codex overview

This PR introduces a light theme to the UI demo, adds dark mode support to Tailwind CSS, and updates the UI to toggle between light and dark themes.

Detailed summary

• Added a light theme to the UI demo
• Implemented dark mode support in Tailwind CSS
• Updated UI to toggle between light and dark themes

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
aa-sdk-site	❌ Failed (Inspect)			Jun 20, 2024 5:53pm

[bswags]

this is above the ...config so that the client apps can override it

[moldy530]

does this also mean that dark mode must be enabled using the dark class?

[bswags]

nope, it handles both! so the OS preference or the class-based approach will work