feat(export): add 6 new services_public settings tables to export

[pyramation]

Summary

Registers the 6 new services_public settings tables (from constructive-db#1060) in the pgpm export system so they are included during database exports.

Tables added: database_settings, api_settings, rls_settings, cors_settings, pubkey_settings, webauthn_settings

Files changed (all in pgpm/export/src/):

• export-utils.ts — field configs in META_TABLE_CONFIG + entries in META_TABLE_ORDER
• export-meta.ts — queryAndParse() calls for SQL export flow
• export-graphql-meta.ts — queryAndParse() calls for GraphQL export flow

Both export flows already handle missing tables gracefully (42P01 catch in SQL, field-not-found catch in GraphQL), so this is safe to merge before or after constructive-db#1060.

Updates since last revision

The field configs for rls_settings, pubkey_settings, and webauthn_settings were updated to match the text→UUID FK conversion in constructive-db#1060 (#816, #817):

• rls_settings: Schema/function text fields → UUID FK fields (e.g. authenticate_schema → authenticate_schema_id, current_role_fn → current_role_function_id)
• pubkey_settings: schema → schema_id, function text fields → *_function_id uuid fields
• webauthn_settings: Schema text fields → *_schema_id, table text fields → *_table_id, added user_field_id uuid FK

database_settings, api_settings, and cors_settings remain unchanged.

Review & Testing Checklist for Human

• Cross-reference field names with constructive-db#1060 deploy SQL — The UUID FK field names in META_TABLE_CONFIG (e.g. authenticate_function_id, sign_up_with_key_function_id, credentials_table_id) must exactly match the column names in the corresponding deploy .sql files. A mismatch won't cause errors (the dynamic field builder silently skips missing columns) but will cause silent data omission during exports.
• api_settings nullable booleans — The DB columns are nullable (boolean without NOT NULL) for inheritance semantics, but the config types them as 'boolean'. Confirm buildDynamicFields() / mapPgTypeToFieldType() handles nullable bool columns correctly (the PG udt_name is bool regardless of nullability, so this should be fine, but worth a sanity check).
• Run a local export against a database that has these tables deployed (after merging constructive-db#1060) to verify the full round-trip produces valid SQL INSERT statements, especially for the UUID FK columns.

Notes

• Related: constructive-planning#814 tracks genericizing the export to auto-discover tables, eliminating the need for these manual additions in the future.

Link to Devin session: https://app.devin.ai/sessions/94a2728a9c414500bead29cbbc829c15
Requested by: @pyramation

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring