The plural form of a table causes conflict if the non-plural version also exists
### Summary

If a schema has similar tables such as "Region" and "Regions", postgraphile will break during setup.

### Steps to reproduce

1. Have tables "Region" and another "Regions".
2. Run postgraphile.
3. Get this error:
A serious error occurred when building the initial schema. Exiting because `retryOnInitFail` is not set. Error details:

Error: A type naming conflict has occurred - two entities have tried to define the same type 'RegionsOrderBy'. 

You can rename the table's GraphQL type via a 'Smart Comment':
    
      COMMENT ON TABLE "public"."region" IS E'@name newNameHere';

### Expected results

Posgraphile should start without problems.

### Actual results

After running the COMMENT command suggested, we get this warning message when running:

SERIOUS WARNING: two GraphQL types (Region and NewRegionNameHere) are trying to use the same node alias 'regions' which may mean that the Relay Global Object Identification identifiers in your schema may not be unique. To solve this, you should skip the PgNodeAliasPostGraphile plugin, but note this will change all your existing Node IDs. For alternative solutions, get in touch via GitHub or Discord

### Additional context
node --version
v18.3.0

psql --version
psql (PostgreSQL) 14.3


### Possible Solution

Naively add 's' to the end of each table when making the API, but offer a config option to specify different ways to alias manually. 

Perhaps related to issue #191. 
