Type safety with custom resolvers and `selectGraphQLResultFromTable`
### Summary

Is it possible to have type-safe queries in [makeExtendSchemaPlugin](https://www.graphile.org/postgraphile/make-extend-schema-plugin/) resolvers, so that the resolvers break at build time if incompatible database schema changes are made?

### Details

I've been following the [makeExtendSchemaPlugin](https://www.graphile.org/postgraphile/make-extend-schema-plugin/) docs and have written some custom resolvers.

I've converted my resolvers to TypeScript and have used [Zapatos](https://jawj.github.io/zapatos/) to generate a TypeScript schema from the DB. Now I get squiggly lines in my IDE and compile errors if my queries don't match the database schema (see images below)

This is perfect, but I don't see a way to get the same type-safety when using the `selectGraphQLResultFromTable` query builder. This means the resolvers may still compile if I change the schema, but fail at runtime.

I've tried building the queries using Zapatos and using a hacked version of the resulting SQL in the query builder using `sql.raw()`, but this seems like a bad idea.

Is there some way to get type safety when using `selectGraphQLResultFromTable`? If not, could I start a feature-request discussion to have Postgraphile generate a TypeScript schema to be used with `pgClient` and `selectGraphQLResultFromTable`?

### Additional context

#### Squigglies in VS Code
![image](https://user-images.githubusercontent.com/1980929/182587802-1146245c-4406-4bf5-81ca-ef77e102cdc4.png)

#### TypeScript compile errors
![image](https://user-images.githubusercontent.com/1980929/182587674-5bee707f-e4cd-48ba-9eae-8b70224963a0.png)