pgResources get() does not return composite types
<!-- Before opening an issue: if you use `npm` try running `yarn` instead; if
      you run `yarn`, please try running `npx yarn-deduplicate && yarn`. -->

### Summary

When you call build.input.pgRegistry.pgResources.some_table.get(), the resulting value does not include columns that are composite types.

### Steps to reproduce

I created a minimal repro here:

https://github.com/jcgsville/dataplan-pg-composite-type-repro

To repro:

1. Create a database `dataplan_pg_composite_type_repro`
2. Run the migration statements in `migration.sql` in `dataplan_pg_composite_type_repro` database
3. npm install
4. node index.js
5. execute the following GraphQL mutation:

```gql
mutation MyMutation {
  doSomething {
    foo {
      aa
    }
  }
}
```

See output logs:

```sh
node index.js
(node:89428) [MODULE_TYPELESS_PACKAGE_JSON] Warning: Module type of file:///path-to-repo/dataplan-pg-composite-type-repro/index.js is not specified and it doesn't parse as CommonJS.
Reparsing as ES module because module syntax was detected. This incurs a performance overhead.
To eliminate this warning, add "type": "module" to /path-to-repo/dataplan-pg-composite-type-repro/package.json.
(Use `node --trace-warnings ...` to show where the warning was created)
The GRAPHILE_ENV environmental variable is not set; Grafast will run in production mode. In your development environments, it's recommended that you set `GRAPHILE_ENV=development` to opt in to additional checks that will provide guidance and help you to catch issues in your code earlier, and other changes such as formatting to improve your development experience.
Server listening at http://localhost:5678
!!!foo [ '1', 0 ]
```


### Expected results

I'd expect to see the `bb` composite type column. e.g.`!!!foo ['1', 0, '(z, y)']`

### Actual results

Prints: `!!!foo [ '1', 0 ]`

### Additional context

Node.js version: `22.12.0`
PostGraphile version: `5.0.0-beta.37`
Postgres version: `17.2`

### Possible Solution

I'm not yet deep enough into Postgraphile internals to suggest a fix 🙂