feat: add org_secrets_module to export pipeline

[pyramation]

Summary

Adds org_secrets_module to the pgpm export pipeline so that the new organization-scoped encrypted secrets config table (added in constructive-db#1209) is included in database exports.

Three files updated, all following the existing pattern for other module exports:

• export-utils.ts: adds org_secrets_module to META_TABLE_ORDER and META_TABLE_CONFIG (fields: id, database_id, schema_id, table_id, table_name)
• export-meta.ts: adds the SQL queryAndParse call
• export-graphql-meta.ts: adds the GraphQL queryAndParse call

Review & Testing Checklist for Human

• Verify the META_TABLE_CONFIG fields (id, database_id, schema_id, table_id, table_name) match the actual metaschema_modules_public.org_secrets_module table columns in constructive-db — cross-reference with the table DDL
• Run an export against a database provisioned with org_secrets_module and verify the org_secrets_module config row appears in the output

Notes

• This is purely additive. The buildDynamicFields() mechanism in the SQL export path gracefully skips the table if it doesn't exist, so this change is safe for databases that don't use org_secrets_module.
• Upstream dependency: requires constructive-db#1209 (already merged) which adds the org_secrets_module config table to metaschema_modules_public.

Link to Devin session: https://app.devin.ai/sessions/af039a166f1c4df4a67704c842540835
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