Add PostgREST query parsing as an opt-in dialect

.gitignore

@@ -1,3 +1,4 @@
 downloaded-modules
 node_modules
 npm-debug.log
+dist

package.json

@@ -7,6 +7,10 @@
 		".": {
 			"types": "./dist/index.d.ts",
 			"default": "./dist/index.js"
+		},
+		"./postgrest": {
+			"types": "./dist/dialects/postgrest.d.ts",
+			"default": "./dist/dialects/postgrest.js"
 		}
 	},
 	"files": [
@@ -15,7 +19,7 @@
 	],
 	"scripts": {
 		"build": "tsc",
-		"test": "node --experimental-strip-types --test test/v2/parse.test.ts",
+		"test": "npm run build && node --experimental-strip-types --test test/v2/parse.test.ts test/dialects/postgrest.test.ts test/dialects/postgrest-dist.test.mjs",
 		"typecheck": "tsc --noEmit"
 	},
 	"devDependencies": {

specification/rql-2.0.md

@@ -647,6 +647,12 @@ Honest gaps, recorded rather than mapped away:
 - **Projection aliasing and casting** — `select=alias:column`, `select=column::text`.
   RQL's `Projection` has no rename or cast; a future revision could add an optional
   `as`/`cast` to `Field`.
+- **Operator configuration arguments** — `phfts(english).The%20Fat%20Cats` carries a
+  full-text-search configuration, but `Condition` has no operator-argument slot. A
+  dialect front-end can preserve it in the opaque extension comparator name
+  (`phfts(english)`); that spelling falls outside §4's `fiql-name` grammar and does
+  not round-trip through §7 serialization. A future revision could model arguments
+  separately.
 - **Null ordering** — `order=age.nullsfirst`. `SortKey` (§6) has no nulls placement;
   reserved for a future revision.
 - **Aggregates in projections** — `select=amount.sum()`; RQL keeps aggregation in the