fix: cannot "go to file" when using dynamic routes on Windows

🐛 The bug

The Component Inspector on Nuxt DevTools can't open a file in the editor if using square brackets on the file name (eg: dynamic routes), which works normally on Linux.

🛠️ To reproduce

https://github.com/ojvribeiro/nuxt-devtools-issue

To reproduce is necessary to be in a Windows enviroment:

• Run the attached reproduction
• Click the "Nested Page" link to go to the nested page
• Use the component inspection tool to select the "Nested child" heading

Then see the error in the terminal:

🌈 Expected behavior

It's expected to go to file on component inspection on Windows. I'm not sure since when this bug started to happen. It worked fine some time ago.

ℹ️ Additional context

Nuxt project info: 23:57:39

• Operating System: Windows_NT
• Node Version: v20.13.1
• Nuxt Version: 3.12.4
• CLI Version: 3.11.1
• Nitro Version: -
• Package Manager: pnpm@9.4.0
• Builder: -
• User Config: devtools, compatibilityDate
• Runtime Modules: -
• Build Modules: -

Start by running the linked reproduction on Windows and tracing the Component Inspector's "go to file" path after selecting the nested child heading. Focus on how square brackets in dynamic-route filenames are handled; done means the editor opens the selected file successfully on Windows.