chore(fixtures): bump the pinned pgpm fixture modules to the capabilities release

[pyramation]

Summary

The integration suites that seed with seed.pgpm(repoRoot) (graphql/server-test, graphql/playwright-test, graphile/graphile-function-bindings) deploy the published modules pinned in the root pgpm.json, not local SQL. Those pins were still pre-rename, so every one of those tests was exercising the old permissions-era platform schema even though the renamed modules are published.

-"@constructive-db/apps": "5.0.0",        +"5.1.0"
-"@constructive-db/catalog": "5.0.0",     +"5.1.0"
-"@constructive-db/routing": "6.0.0",     +"6.1.0"
-"@constructive-db/routing-platform": "5.0.0", +"5.1.0"
-"@pgpm/*": "0.33.x"                      +"0.41.0"

Verified after pnpm fixtures:install: the installed @pgpm/metaschema-modules DDL now carries capabilit* columns, and both DB-backed suites are green — graphql/server-test 152/152, graphile/graphile-function-bindings 22/22.

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