sync: repository_module proposals configuration (v0.43.0)

[pyramation]

Summary

Ports the repository_module configuration rename from constructive-db (constructive-io/constructive-db#3165), where the repository module's change-request family became a generic proposal family, and releases it as 0.43.0.

metaschema_modules_public.repository_module config columns:

-change_requests_table_id/…_table_name          -> 'change_requests'
-change_request_comments_table_id/…_table_name  -> 'change_request_comments'
-change_request_reactions_…
-change_request_reviews_…
-change_request_file_views_…
+proposals_table_id/proposals_table_name                  -> 'proposals'
+proposal_comments_table_id/proposal_comments_table_name  -> 'proposal_comments'
+proposal_reactions_…
+proposal_reviews_…
+proposal_file_views_…

FK constraint names, index names and column comments follow the rename; verify/ selects the new column list. Nothing else in the configuration contract changes — the generator that consumes these names lives in constructive-db.

Release

0.43.0 (0.42.0 is already released and this renames columns, so it needs its own version). Version bump + pgpm package output produced by lerna version, as in the v0.42.0 commit.

Testing

• packages/metaschema-modules jest: 8/8 pass (no snapshot referenced the old names)
• pgpm test-packages --full-cycle: ALL MODULES PASSED

Link to Devin session: https://app.devin.ai/sessions/116af8fe48ae4feeb200673bdf34f043
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, CI, and merge conflict monitoring