chore: generate dogfooding test for long pathname during CI

[Josh-Cena]

Motivation

Fix #5793. It would still be cool to verify that things do work, but generating the file during CI ensures Windows contributors don't get unnecessarily hindered by the extra configuration needed.

Have you read the Contributing Guidelines on pull requests?

Yes

Test Plan

Windows tests

[netlify]

✔️ [V2]

🔨 Explore the source changes: 513baa6

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

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

[github-actions]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🟠 Performance	87
🟢 Accessibility	98
🟢 Best practices	100
🟢 SEO	100
🟢 PWA	95

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

[github-actions]

Size Change: -1.35 kB (0%)

Total Size: 890 kB

Filename	Size	Change
website/build/assets/js/main.********.js	476 kB	-1.35 kB (0%)

ℹ️ View Unchanged

Filename	Size	Change
website/.docusaurus/globalData.json	38.3 kB	0 B
website/build/assets/css/styles.********.css	100 kB	0 B
website/build/blog/2017/12/14/introducing-docusaurus/index.html	66.1 kB	0 B
website/build/blog/index.html	36.8 kB	0 B
website/build/docs/index.html	44 kB	+1 B (0%)
website/build/docs/installation/index.html	51.7 kB	-2 B (0%)
website/build/index.html	29.5 kB	0 B
website/build/tests/docs/index.html	25.2 kB	0 B
website/build/tests/docs/standalone/index.html	21.7 kB	0 B

_{compressed-size-action}

[slorber]

👍 thanks ;)