Add `@prisma/prisma-fmt-wasm` to CLI and output dependency version in `-v`, use instead of Formatter Engine binary

@prisma/prisma-fmt-wasm exists and can replace the Formatter Engine binary usage in Prisma CLI already.

1. Add @prisma/prisma-fmt-wasm as dependency (requires CI changes)
2. Output dependency package version in -v output of Prisma CLI
3. Replace the format (and others) call of the Formatter Engine binary with a call to the Wasm module (in a separate PR)
4. Test CLI Engine Crash Reporting along the way to make sure it also works properly with the Wasm module
5. Profit 🚢

[0gust1]

@jkomyno Hi 👋 . Thanks for the follow-up! I’ll open an issue (it was on my today’s TODO, after my yesterday post on https://github.com/prisma/prisma/discussions/15859) and/or post on #15881. Expect some news in the next 6 hours.

Very quickly (those elements – and others – will be in the issue):
It’s a standalone project; I suspect that the azure deployment could “do things” to the node_modules folder; I still can’t completely rule out a problem on our own workflow. Reproductibility won’t be easy (as it will need an Azure account/subscription), but I’ll try.

[0gust1]

We have the same kind of error as @jkomyno posted, when trying to run prisma migrate deploy on our target server.

node: 16.14.2 prisma: 4.4.0 env: Azure AppService (“classic” zip deploy)

Error: ENOENT: no such file or directory, open '/home/site/wwwroot/node_modules/.bin/prisma_fmt_build_bg.wasm'
    at Object.openSync (node:fs:585:3)
    at Object.readFileSync (node:fs:453:35)
    at ../../node_modules/.pnpm/@prisma+prisma-fmt-wasm@4.4.0-66.f352a33b70356f46311da8b00d83386dd9f145d6/node_modules/@prisma/prisma-fmt-wasm/src/prisma_fmt_build.js (/home/site/wwwroot/node_modules/.bin/prisma:12337:31)
    at __require (/home/site/wwwroot/node_modules/.bin/prisma:14:50)
    at Object.<anonymous> (/home/site/wwwroot/node_modules/.bin/prisma:86202:38)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) {
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: '/home/site/wwwroot/node_modules/.bin/prisma_fmt_build_bg.wasm'
}

In node_modules/@prisma/engines we have the correct engines (prisma-fmt-debian-openssl-1.1.x in our case), but it keep searching for a wasm module, at the wrong place (node_modules/.bin/prisma_fmt_build_bg.wasm).
Everything works fine in a local development context.