fix: use percent-encoded DATABASE_URL instead of split DB_PASSWORD trick

Drizzle ORM mutates client.options (parsers/serializers) after the postgres
client is created, which causes the separately-passed password option to be
lost on the actual connection attempt. Root cause confirmed on VPS: raw
postgres.js query succeeded while drizzle.execute() failed with auth error.

Fix: encode the password directly in DATABASE_URL (%23 = #, %5D = ], %3D = =).
postgres.js decodes percent-encoding correctly. No separate DB_PASSWORD env
var needed in the app container anymore.

DB_PASSWORD is still used by the Postgres container (POSTGRES_PASSWORD).
Coolify env var to set: DATABASE_URL=postgres://wc:<encoded-pass>@db:5432/worldcup

Also adds resolver-level isMissingTable() guards so the app returns empty
results instead of GraphQL errors on a fresh deploy before sync runs.

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

scripts/sync.ts

@@ -73,10 +73,7 @@ function parseScore(score: RawScore | undefined) {
 }
 
 async function run() {
-  const client = postgres(DATABASE_URL, {
-    max: 5,
-    ...(process.env.DB_PASSWORD ? { password: process.env.DB_PASSWORD } : {}),
-  })
+  const client = postgres(DATABASE_URL, { max: 5 })
   const db = drizzle(client)
 
   console.log('Creating tables...')