ci: add a workaround for test case on Windows

[JounQin]

https://github.com/mdx-js/mdx-analyzer/actions/runs/7103468527/job/19336238880#step:5:92

I believe this could be a vscode core issue.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f9cf44e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[wooorm]

@remcohaszing Isn’t that a difference between VS Code URLs (paths) and Node URL object’s href? 🤔

[JounQin]

@remcohaszing Isn’t that a difference between VS Code URLs (paths) and Node URL object’s href? 🤔

@wooorm Yes, that's why I mentioned

I believe this could be a vscode core issue.

+               path: '/d:/a/mdx-analyzer/mdx-analyzer/fixtures/node16/link-reference.mdx.md',
-               path: 'd:/a/mdx-analyzer/mdx-analyzer/fixtures/node16/link-reference.mdx.md',

[remcohaszing]

I’m not really sure why this was happening. I though the issue was introduced by in #356, so it was fixed there before merging.

I’m not really sure why VS Code uses vscode-uri, and why it’s subtly different from Node’s URL. It is very annoying though.

[github-actions]

Hi! This was closed. Team: If this was merged, please describe when this is likely to be released. Otherwise, please add one of the no/* labels.