feat: rename user_secrets_module/org_secrets_module to config_secrets_user_module/config_secrets_org_module

[pyramation]

Summary

Renames module identifiers to match the upstream rename in constructive-db #1219:

• user_secrets_module → config_secrets_user_module
• org_secrets_module → config_secrets_org_module

Three areas updated:

1. Module presets (7 files) — modules arrays and includes_notes in all auth/b2b presets
2. Export pipeline (3 files) — META_TABLE_ORDER, META_TABLE_CONFIG keys/table names, SQL queries in export-meta.ts, and GraphQL query keys in export-graphql-meta.ts
3. Tests (2 files) — expected module names in export-meta.test.ts and GraphQL naming assertions in graphql-naming.test.ts

No functionality changes — purely a naming alignment.

Review & Testing Checklist for Human

• Merge ordering: constructive-db #1219 must be merged first — this PR queries metaschema_modules_public.config_secrets_user_module / config_secrets_org_module tables that only exist after the DB rename lands
• Completeness: grep the repo for any remaining \buser_secrets_module\b or \borg_secrets_module\b references that may have been missed (note: session_secrets_module is a different module and should NOT be renamed)
• GraphQL name derivation: verify that PostGraphile will expose config_secrets_user_module as configSecretsUserModules (the getGraphQLQueryName function is generic camelCase+pluralize, so this should be automatic, but worth confirming against a live schema)

Notes

• The session_secrets_module references in the export pipeline are intentionally unchanged — that is a separate module
• auth-sso.ts has documentation strings that also referenced the old name; those were updated too

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