fix(graphile-postgis): remove isPgConnectionFilterMany scope to avoid some/every/none collision

Setting isPgConnectionFilterMany: true on our per-relation spatial
filter type caused ConnectionFilterBackwardRelationsPlugin to
auto-register some/every/none fields with FK-join semantics — colliding
with (and semantically different from) the ones we register. Our
plugin fully owns those fields for spatial-relation filter types, so
we leave that flag off.

Author: pyramation

graphile/graphile-postgis/src/plugins/spatial-relations.ts

@@ -572,7 +572,11 @@ export const PostgisSpatialRelationsPlugin: GraphileConfig.Plugin = {
             build.registerInputObjectType(
               typeName,
               {
-                isPgConnectionFilterMany: true,
+                // NOTE: intentionally NOT setting `isPgConnectionFilterMany`.
+                // That flag triggers ConnectionFilterBackwardRelationsPlugin
+                // (and friends) to auto-register `some`/`every`/`none` fields
+                // with FK-join semantics, which would collide with — and
+                // semantically differ from — ours. We own those fields here.
                 foreignTable: rel.targetResource,
                 isPgGISSpatialFilter: true,
                 pgGISSpatialRelation: rel,