fix(client): replace dynamic import for wasm-worker-loader with static export

[smorimoto]

Fixes #23600

As I understand, since dynamic import is not necessary here, we can easily fix the linked issue.
Is there anything I am missing?
I'm actually using this patch in my runtime environment and I don't see any performance issues either.

[CLAassistant]

All committers have signed the CLA.

[jkomyno]

Thank you @smorimoto for this PR.
I think the next course of action for us is to merge this and observe the impact on our ecosystem-tests.

To summarise the context around this PR for other internal reviewers:

• Next.js uses a non-standard top-level await plugin, which can conflict with how we use import the Wasm Query Engine in Prisma: Top level await with SWC vercel/next.js#31054
• Some users reported similar errors on Next.js + other libraries different than Prisma: Edge runtime causing terser panic due to top level await vercel/next.js#64792 (comment)
• Some of the Next.js + Prisma users reported that the patch provided by this PR works: Next.js app build fails when using Prisma with DB driver in Server Action #23600 (comment)
• It looks like recent versions of Next.js 14 recently surfaced this problem to runtime = "edge" users: Edge runtime causing terser panic due to top level await vercel/next.js#64792 (comment)

[Vinlock]

Nice! Glad this is getting fixed. Thank you 🙏🏼 🙏🏼 🙏🏼 🙏🏼