fix: prevent theme switcher from overwriting saved theme on mount

[snowopsdev]

What does this PR do?

Fixes a bug where ThemeSwitcher overwrites the user's saved localStorage theme with the default 'dracula' theme on the initial render.

Problem

Previously, the second useEffect in ThemeSwitcher ran immediately on mount, writing the initial component state ('dracula') to localStorage before the first useEffect had a chance to apply the saved theme. This caused a flash of unstyled content and overwrote user preferences if the state didn't update fast enough or if multiple storage events fired.

Solution

• Added a mounted state to defer the localStorage write until the component is fully mounted.
• Updated the initial effect to apply the saved theme directly to the DOM when found, preventing the visual flash while React batches the state update.

Type of Change

• 🐛 Bug fix

Checklist

• Component works correctly
• Build passes

[vercel]

@voqthekid is attempting to deploy a commit to the 0xBuns Team on Vercel.

A member of the Team first needs to authorize it.

[BunsDev]

Maintainer triage: keeping this open as one of the highest-value bugfixes in the queue. The change is narrowly scoped, addresses a real mount-time theme persistence bug, and does not overlap with the feature backlog. Once the branch is current with main, this is a strong candidate for merge ahead of most component-addition PRs.

[BunsDev]

Maintainer note: repo-owned Actions are now enabled and branch protection is live, but this PR still needs a fresh branch update from current main to pick up the corrected CI workflow definition. The rerun above is still using the pre-fix workflow snapshot, so treat the current Typecheck & Build failure as stale once the branch is refreshed.

[BunsDev]

Reviewed after branch refresh. The fix is narrowly scoped, the repo-owned checks now pass, and this remains a strong early merge candidate.