refactor(safegres): drop Authz* re-exports + node-type-registry dep

The pure-Postgres auditor doesn't use Authz* anywhere — its findings
(A1–A7, P1, P5) are catalog/AST checks with no Constructive-template
knowledge. Re-exporting Authz* values + JSON-Schema configs from a
public MIT package would leak the Constructive policy DSL.

Consumers that need Authz* (rls-audit in constructive-db) can import
directly from node-type-registry. safegres no longer depends on it.

Author: pyramation

graphql/safegres/package.json

@@ -46,7 +46,6 @@
     "@pgsql/traverse": "^17.2.5",
     "@pgsql/types": "^17.6.2",
     "inquirerer": "^4.7.0",
-    "node-type-registry": "workspace:^",
     "pg": "^8.16.0",
     "pg-env": "^1.9.0",
     "pgsql-deparser": "^17.18.2",

graphql/safegres/src/index.ts

@@ -4,10 +4,6 @@
  * The auditor introspects pg_class / pg_policy / role grants and emits
  * structured findings (A1–A7, P1, P5). It has no knowledge of any specific
  * application schema or policy DSL.
- *
- * For convenience, `node-type-registry`'s Authz* / Data* / Relation* / View*
- * type definitions are re-exported here so consumers building auditors on
- * top of Constructive's type system only need a single dependency.
  */
 
 export { auditPg } from './commands/pg';
@@ -31,23 +27,3 @@ export {
   type PgAstNode,
   type PolicyExpression
 } from './ast/parse';
-
-export type { JSONSchema, NodeTypeDefinition } from 'node-type-registry';
-export {
-  AuthzAllowAll,
-  AuthzComposite,
-  AuthzDenyAll,
-  AuthzDirectOwner,
-  AuthzDirectOwnerAny,
-  AuthzEntityMembership,
-  AuthzMemberList,
-  AuthzMembership,
-  AuthzNotReadOnly,
-  AuthzOrgHierarchy,
-  AuthzPeerOwnership,
-  AuthzPublishable,
-  AuthzRelatedEntityMembership,
-  AuthzRelatedMemberList,
-  AuthzRelatedPeerOwnership,
-  AuthzTemporal
-} from 'node-type-registry';