fix: make component testing windows compatible

[elevatebart]

• Closes [7.0.0] Doesn't display list of specs in Cypress Component Test Runner #15842

User facing changelog

Repair the component testing build for windows

Additional details

• Forked https://github.com/liximomo/lazy-compile-webpack-plugin to make it windows compatible (following liximomo's advice of the original PR)
• Made relative paths of specs on windows use forward slash instead of backslash for POSIX compatible paths. Allowing the runner-ct to parse them on the front-end into directories.

How has the user experience changed?

Now Component Testing works on windows

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[cypress]

---

Test summary

9492 • 0 • 111 • 3 • 1

---

Run details

Project	cypress
Status	Passed
Commit	fcae3b4
Started	Apr 9, 2021 9:48 PM
Ended	Apr 9, 2021 10:00 PM
Duration	12:34 💡
OS	Linux Debian - 10.8
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	cypress/integration/retries.ui.spec.js		1
1	runner/cypress retries.ui.spec > opens attempt on each attempt failure for the screenshot, and closes after test passes

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[lmiller1990]

One comment... don't we have some way to run windows on CI? 🤔

[elevatebart]

@lmiller1990 I believe we might be able to do that on AppVeyor.
CircleCI recently added it too.
I would still merge this without a test and figure out a way to test it in a future PR

[lmiller1990]

@JessicaSachs @elevatebart this should be merged right, not closed?

[cypress-bot]

Released in 7.1.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v7.1.0, please open a new issue.