fix(theme-common): do not run useLocationChange when hot reloading

[lex111]

Motivation

Just noticed that we have the problem described in the issue again > #4794

This is still caused by the SkipContent component, but actually because the useLocationChange hook was triggered when it was not expected (changed doc -> hot reload -> re-render, but in fact the current location has not changed).

Have you read the Contributing Guidelines on pull requests?

Yes

Test Plan

1. Start dev server
2. Go to any doc page and scroll it a bit
3. Edit any doc
4. The scroll position of the current doc page should same as before

Related PRs

[netlify]

✔️ [V2]

🔨 Explore the source changes: 469fce0

🔍 Inspect the deploy log: https://app.netlify.com/sites/docusaurus-2/deploys/620d7ff4cdfa150007250794

😎 Browse the preview: https://deploy-preview-6696--docusaurus-2.netlify.app

[github-actions]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🟠 Performance	69
🟢 Accessibility	100
🟢 Best practices	100
🟢 SEO	100
🟢 PWA	92

Lighthouse ran on https://deploy-preview-6696--docusaurus-2.netlify.app/

[github-actions]

Size Change: +3 B (0%)

Total Size: 781 kB

ℹ️ View Unchanged

Filename	Size	Change
website/.docusaurus/globalData.json	48 kB	0 B
website/build/assets/css/styles.********.css	106 kB	0 B
website/build/assets/js/main.********.js	590 kB	+3 B (0%)
website/build/index.html	37.6 kB	0 B

_{compressed-size-action}

[gerhard]

This was extremely annoying when iterating locally on docs. Thank you for this fix!

I applied it manually and look forward to upgrading to the Docusaurus beta that will include it 🙌🏻

cc @slumbering

[Josh-Cena]

This has been annoying for me as well. Glad you found the fix!