fix: align plugin SQL with actual DB schema (mime_type, no content_hash on files)

[pyramation]

Summary

Fixes a schema mismatch between the presigned-url-plugin's raw SQL and the actual files table generated by storage_module.sql in constructive-db.

The generated files table uses mime_type (not content_type) and has no content_hash column — content_hash only exists on the upload_requests table. The file's S3 key (stored in the key column) already equals the content hash since buildS3Key(contentHash) returns the hash directly.

Changes:

• Dedup check (plugin.ts): WHERE content_hash = $1 → WHERE key = $1
• File INSERT (plugin.ts): Column list uses mime_type instead of content_type; drops content_hash (and adjusts positional $N params accordingly)
• confirmUpload (plugin.ts): file.content_type → file.mime_type in S3 HEAD verification and error messages
• resolveStorageModuleByFileId (storage-module-cache.ts): SELECT and TypeScript types updated from content_type to mime_type
• Test fixture (schema.sql): files table updated to use mime_type and drop content_hash to match the generated schema

The upload_requests INSERT is intentionally unchanged — that table does have content_type and content_hash columns.

Review & Testing Checklist for Human

• Verify column/value alignment in the file INSERT: Removing content_hash shifted all positional params ($N). Confirm the with-owner branch (7 columns → 7 values) and without-owner branch (6 columns → 6 values) are correctly aligned
• Verify the dedup check is semantically correct: key on files stores the S3 key which equals the content hash. Confirm WHERE key = $1 AND bucket_id = $2 is a valid dedup strategy (there should be a unique index or constraint backing this)
• Run the upload integration test (graphql/server-test) end-to-end against a provisioned database to confirm requestUploadUrl → PUT → confirmUpload works with the corrected column names

Notes

• This bug was introduced in PR feat: multi-scope bucket resolution (Option C: bucketKey + ownerId) #1009 (multi-scope bucket resolution) where the plugin SQL was written against assumed column names rather than the actual generated schema
• Blocking the MinIO integration test in constructive-db PR Revert "fix(graphql-codegen): re-export input types from generated ORM index" #891 — that test cannot pass until this fix is published

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