Fix duplicate template seeding in email-api migrations

Remove Seed() call from CreateEmailTemplates Up() method to prevent
duplicate key violation when applying SeedEmailTemplates migration.

The original migration was attempting to seed data during schema creation,
but data seeding is now handled by the separate SeedEmailTemplates migration
(20260528130652). Keeping both Seed() calls caused PRIMARY KEY violation on
(email.html-shell.start, *) when the second migration tried to insert
already-existing templates.

This maintains the migration order: schema creation first, then data seeding
in a separate, dedicated migration.

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

Apis/email-api-data/Migrations/20260528100000_CreateEmailTemplates.cs

@@ -29,8 +29,6 @@ namespace EmailApi.Data.Migrations
                 {
                     table.PrimaryKey("PK_EmailTemplates", x => new { x.Key, x.Language });
                 });
-
-            Seed(migrationBuilder);
         }
 
         private static void Seed(MigrationBuilder m)

docker-compose/docker-compose.yml

@@ -116,7 +116,7 @@ services:
       - Database__TrustServerCertificate=${Database__TrustServerCertificate:-true}
 
       - InternalApi__ApiKey=${EmailApi__InternalApiKey:-}
-      - InternalApi__RequireApiKey=true
+      - InternalApi__RequireApiKey=${EmailApi__RequireApiKey:-true}
 
       - Smtp__Host=${Smtp__Host:-}
       - Smtp__Port=${Smtp__Port:-587}