Vitest crashes on throwing non object data

[Akiyamka]

Describe the bug

In TypeScript error always have unknown type, because it's will be valid case if code throw nothing or some primitive.
But vitest not expect that, and crashes in attempt to read error properties

Reproduction

  test.only('test', async () => {
    throw 'blablaError'
    expect(true).toBe(true);
  })

Error:

TypeError: Cannot read properties of undefined (reading 'stacks')
 ❯ parseStacktrace node_modules/vitest/dist/chunk-utils-source-map.bbf3ad19.mjs:5679:1
    5677|     return [urlLike];
    5678|   return [parts[1], parts[2] || void 0, parts[3] || void 0];
    5679| }
       | ^
    5680| function parseStacktrace(e, full = false) {
    5681|   if (e.stacks)
 ❯ printError node_modules/vitest/dist/chunk-vite-node-externalize.c843f497.mjs:9214:18
 ❯ Logger.printError node_modules/vitest/dist/chunk-vite-node-externalize.c843f497.mjs:9406:12
 ❯ DefaultReporter.printTaskErrors node_modules/vitest/dist/chunk-vite-node-externalize.c843f497.mjs:7542:29
 ❯ DefaultReporter.reportSummary node_modules/vitest/dist/chunk-vite-node-externalize.c843f497.mjs:7488:18
 ❯ process.processTicksAndRejections node:internal/process/task_queues:95:5
 ❯ DefaultReporter.onFinished node_modules/vitest/dist/chunk-vite-node-externalize.c843f497.mjs:7340:5
 ❯ DefaultReporter.onFinished node_modules/vitest/dist/chunk-vite-node-externalize.c843f497.mjs:7681:5
 ❯ Vitest.report node_modules/vitest/dist/chunk-vite-node-externalize.c843f497.mjs:9801:5

System Info

System:
    OS: Linux 5.18 Fedora Linux 36 (Workstation Edition)
    CPU: (16) x64 AMD Ryzen 7 5800H with Radeon Graphics
    Memory: 4.81 GB / 13.50 GB
    Container: Yes
    Shell: 5.8.1 - /usr/bin/zsh
  Binaries:
    Node: 18.7.0 - ~/n/bin/node
    Yarn: 1.22.19 - ~/n/bin/yarn
    npm: 8.15.0 - ~/n/bin/npm
  Browsers:
    Firefox: 103.0.1

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.