Snapshot file path different in CI causing failure

[MichaelFBA]

Describe the bug

When using snapshots in vitest the __file path is different in dev / ci causing the test to fail in CI

expect(wrapper).toMatchSnapshot();

 FAIL  src/pages/product-list.spec.ts > ProductList > should render component
AssertionError: Snapshot `ProductList > should render component 1` mismatched
 ❯ src/pages/product-list.spec.ts:11:20
      9|     const wrapper = mount(ProductList);
     10| 
     11|     expect(wrapper).toMatchSnapshot();
       |                    ^
     12|   });
     13| });

  - Expected  - 2
  + Received  + 2
  
              },
              "suspense": null,
              "suspenseId": 0,
              "type": {
  -             "__file": "/LOCAL_DEVELOPMENT_PATH…
  +             "__file": "/********/src/github.com/<CI_PATH>…
                "components": {},
                "render": [Function],
                "setup": [Function],
              },
  --
            "target": null,
            "targetAnchor": null,
            "transition": null,
            "type": {
  -           "__file": "<LOCAL_DEVELOPMENT_PATH>…
  +           "__file": "/********/src/github.com/<CI_PATH>…
              "components": {},
              "render": [Function],
              "setup": [Function],
            },

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯

 Snapshots  1 failed
Test Files  1 failed (1)
     Tests  1 failed (1)
      Time  5.43s (in thread 21ms, 25862.25%)
      ```

### Reproduction

its difficult to setup a CI test

### System Info

```shell
System:
    OS: Linux 5.15 Ubuntu 20.04.3 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
    Memory: 15.50 GB / 31.02 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 1.22.15 - ~/.nvm/versions/node/v16.13.1/bin/yarn
    npm: 8.13.1 - ~/.nvm/versions/node/v16.13.1/bin/npm
  Browsers:
    Chrome: 97.0.4692.71
    Firefox: 102.0
  npmPackages:
    @vitejs/plugin-vue: ^2.3.3 => 2.3.3 
    vite: ^2.9.7 => 2.9.7 
    vitest: ^0.18.0 => 0.18.0 

### Used Package Manager

npm

### Validations

- [X] Follow our [Code of Conduct](https://github.com/vitest-dev/vitest/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitest-dev/vitest/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitest.dev/guide/).
- [X] Check that there isn't [already an issue](https://github.com/vitest-dev/vitest/issues) that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitest-dev/vitest/discussions) or join our [Discord Chat Server](https://chat.vitest.dev).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

[sheremet-va]

This is not an issue with Vitest. If you are making snapshots of Vue components, it's better to use wrapper.element.

[joaopedrodcf]

You are the real MVP thanks 🎖️