fix: resolve PostgreSQL migration issues for development environment

- Added DATABASE_CLIENT=pg to docker-compose.dev.yml for PostgreSQL connection
- Fixed migration 032 to check if tables exist before creating
- Removed language-specific email template columns (use standard columns)
- Added conditional checks for app_settings and email_templates inserts
- Created helper scripts for migration state management
- Added .env.dev with PostgreSQL configuration for development

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

backend/scripts/mark-migration-applied.js

@@ -0,0 +1,46 @@
+#!/usr/bin/env node
+
+/**
+ * Mark a specific migration as applied without running it
+ * Usage: node scripts/mark-migration-applied.js <migration-filename>
+ */
+
+const { db } = require('../src/database/db');
+
+async function markMigrationAsApplied(filename) {
+  try {
+    // Check if migration is already marked
+    const existing = await db('migrations')
+      .where('filename', filename)
+      .first();
+    
+    if (existing) {
+      console.log(`Migration ${filename} is already marked as applied`);
+      return;
+    }
+    
+    // Mark as applied
+    await db('migrations').insert({ 
+      filename,
+      applied_at: new Date()
+    });
+    
+    console.log(`✅ Migration ${filename} marked as applied`);
+  } catch (error) {
+    console.error('Error marking migration:', error.message);
+    process.exit(1);
+  } finally {
+    await db.destroy();
+  }
+}
+
+// Get migration filename from command line
+const migrationFile = process.argv[2];
+
+if (!migrationFile) {
+  console.error('Usage: node scripts/mark-migration-applied.js <migration-filename>');
+  console.error('Example: node scripts/mark-migration-applied.js 032_add_restore_runs_table.js');
+  process.exit(1);
+}
+
+markMigrationAsApplied(migrationFile);