PR Checklist

On Windows generated paths are ./app.component.css|C:/path/to/src/app.component.css rather than ./app.component.css|/path/to/src/app.component.css, causing tests to fail. Trying to understand where this issue is coming from, I found some older PRs (#275 and #799), that tried to utilize vite's normalizePath(), which used to also take care of Windows' drive letters, though that was ages ago.

Closes #1860

What is the new behavior?

1. ./app.component.css|/path/to/src/app.component.css now properly maps to ./app.component.css|/path/to/src/app.component.css.
2. I changed the helper function into a proper matcher, making it easier in the future to see what the problem is:

// Previously
Expected: true
Received: false

// Now (roughly)
- Expected
+ Received
[
  -./app.component.css|/path/to/src/app.component.css
  +./app.component.css|C:/path/to/src/app.component.css
]

3. Removed redundant .replace(/\\/g, '/') which is already taken care of by normalizePath().
4. Changed nomenclature in test to reflect typical test nomenclature, reducing ambiguity. E.g. actualPaths -> expectedPaths because actual actual paths 😏 are generated by the resolver.

Does this PR introduce a breaking change?

• Yes
• No