[BUG] - Fix tailwind themes in docs

[itaismith]

Description of changes

Tailwind dark-mode did not respond to changes properly since next-themes uses data-theme="dark" to apply dark mode styling to elements in this project.

This made it hard to develop dark mode styling for custom components on the docs site.

Test plan

Visually tested with npm run dev. Notice that in production the "sun" doesn't change to a "moon" when applying dark mode (this should happen on the tailwind styling).

Documentation Changes

Not needed.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[jeffchuber]

@itaismith the header is the wrong color - will dig in more tonight

[itaismith]

@jeffchuber If you remove dark:bg-stone-950 from line 13 in TopNav.tsx it should default to the ShadCn coloring we have in prod. This style wasn't applied before because the tailwind dark mode wasn't actually working.

I went ahead and removed it!

[jeffchuber]

ty! 🫡