fix: reintroduce source-map support

[Weakky]

closes #1107

I don't remember why we ditched ts-node but I don't see the point so far. We're keeping it in our dependencies regardless to enable folks to run their prisma seed script. Maybe ts-node should only be part of the prisma plugin. Point is, it's a very light dependency anyway and it prevents issues like the one I just fixed.

This PR re-enables pretty traces used in nexus-plugin-prisma.

TODO

• docs
  • jsdoc
  • website api
  • website guides
  • website tutorial
• tests

[jasonkuhrt]

Awesome!

I opted to not use ts-node internally to stay closer to the metal and not have some parts using ts-node while others not. We need to own our TS experience and I don’t understand all the things ts-node is or isn’t doing.