fix: use upstream node-sql-parser package

This changes Yates to use the original upstream node-sql-parser package.
The only reason Yates uses my fork is because at the time the
`exprToSQL` method I contributed was not available in the general
release. Fast-forward to 10 months later and my fork is now 499 commits
behind master XD
The only real difference that has to be made is the way that `$n`
parameters are represented in the AST, but this is a simple change to
make.

Signed-off-by: Lucian Buzzo <lucian.buzzo@gmail.com>

package.json

@@ -29,7 +29,7 @@
     "uuid": "^9.0.0"
   },
   "dependencies": {
-    "@lucianbuzzo/node-sql-parser": "^4.6.6",
+    "node-sql-parser": "^4.12.0",
     "lodash": "^4.17.21"
   },
   "peerDependencies": {

src/expressions.ts

@@ -2,7 +2,7 @@ import { Prisma, PrismaClient } from "@prisma/client";
 import { Dictionary, get } from "lodash";
 import random from "lodash/random";
 import matches from "lodash/matches";
-import { Parser } from "@lucianbuzzo/node-sql-parser";
+import { Parser } from "node-sql-parser";
 import { escapeIdentifier, escapeLiteral } from "./escape";
 import { RuntimeDataModel } from "@prisma/client/runtime/library";
 
@@ -254,8 +254,9 @@ export const expressionToSQL = async (getExpression: Expression, table: string):
 
 						const parameterizedStatement = deepFind(ast, {
 							right: {
-								type: "origin",
-								value: `$${i + 1}`,
+								type: "var",
+								name: i + 1,
+								prefix: "$",
 							},
 						});