Support path mapping and vscode:// protocol for use in containerized environments

[abcRede]

Is your feature request related to a problem? Please describe.

Currently, when using vite-plugin-checker in a Docker container, the file paths reported for issues in browser differ from the real file paths on the host machine where I have VSCode open. This leads to an error like:
Could not open MyFile.vue in the editor. on terminal, after clicking in the linted file.

Even when using the Dev Container feature of VSCode, this problem persists.

Describe the solution you'd like

I suggest implementing support for opening files using the vscode://file protocol. This would allow vite-plugin-checker to include clickable links for file paths that resolve correctly in VSCode, even when running inside a Docker container.

Additionally, a configuration option could be added to map container paths to host paths. For example:

checker({
  eslint: {
    filePathMap: {
      '/app': '/Users/username/project'
    }
  }
})

Describe alternatives you've considered

No response

Additional context

No response

Validations

• Read the docs.
• Read the Contributing Guidelines.
• Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.