fix(website): ensure feedback widget renders with correct theme

[p-m-p]

If a user lands on the feature request community page with the theme set to dark the canny widget is rendered twice, first light and then dark. The first call with the light theme takes effect as the widget has not yet loaded and the widget shows in light theme. Adding a small delay prevents the first render with the wrong theme.

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Test links

Deploy preview: https://deploy-preview-11224--docusaurus-2.netlify.app/

[netlify]

✅ [V2]

Name	Link
🔨 Latest commit	5081557
🔍 Latest deploy log	https://app.netlify.com/projects/docusaurus-2/deploys/683d78fd7a078d000888131b
😎 Deploy Preview	https://deploy-preview-11224--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	Report
/	🟠 68	🟢 98	🟢 100	🟢 100	Report
/docs/installation	🟠 50	🟢 97	🟢 100	🟢 100	Report
/docs/category/getting-started	🟠 72	🟢 100	🟢 100	🟠 86	Report
/blog	🟠 59	🟢 96	🟢 100	🟠 86	Report
/blog/preparing-your-site-for-docusaurus-v3	🔴 45	🟢 92	🟢 100	🟢 100	Report
/blog/tags/release	🟠 61	🟢 96	🟢 100	🟠 86	Report
/blog/tags	🟠 72	🟢 100	🟢 100	🟠 86	Report

[slorber]

Hey thanks for noticing this little bug

I'm not a fan of setTimeout with magic values, so I changed the fix for a better implementation.

---

Although both solutions work and fix the issue, the root source of the error is due to useColorMode(), which is a quite misleading historical hook we have.

On first render, it always returns the "default" theme we use during SSG to avoid React hydration mismatches. And the ColorModeProvider is applied by the Layout component, which resets the color mode state when you navigate to this page.

TLDR, during both initial load (hydration) and navigation, the useColorMode() always returns initially "light" (even if you are effectively in dark mode), and then eventually switch to "black". The canny problem only appears for the initial load by chance, but in both cases, canny is called first with "light" and then called with "dark". We should ensure that at most, canny is initialized only once.

We should find a way to fix the root cause, but it likely requires a breaking change to the publicly documented useColorMode() hook, so I noted to take another look at this for v4. Until then, fixing the symptom (and not the cause) is good enough.