fix: update remaining db-meta-schema reference to metaschema-schema in fixture dependency

[pyramation]

Summary

Fixes a missed reference from the db-meta to metaschema rename. The metaschema-modules fixture's pgpm.plan file still had a dependency reference to db-meta-schema instead of metaschema-schema.

This was causing the test getModules() returns all modules from extensions/@pgpm and packages in stage-workspace.test.ts to fail when checking for metaschema module names.

Review & Testing Checklist for Human

• Verify the dependency reference metaschema-schema:schemas/meta_public/tables/site_themes/table is correct and matches the actual module name in __fixtures__/stage/extensions/@pgpm/metaschema-schema/pgpm.plan

Test Plan

Run the stage-workspace tests to verify the fix:

cd pgpm/core && pnpm test -- __tests__/projects/stage-workspace.test.ts

Notes

• This completes the db-meta → metaschema rename that was mostly done in PR Revert: Undo Blacksmith migration from PR #559 #561
• Link to Devin run: https://app.devin.ai/sessions/6497dd7a81524f12a8adce47724ed35c
• Requested by: Dan Lynch (@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