refactor(data): rename email-api-data to email-data for consistent naming

- Rename project folder Apis/email-api-data → Apis/email-data
- Rename csproj file: email-api-data.csproj → email-data.csproj
- Update csproj properties: AssemblyName and RootNamespace (email-data, Email.Data)
- Update C# namespaces: EmailApi.Data → Email.Data across all email-data files
- Update project references in api.csproj and email-api.csproj
- Update migration assembly references in api/Program.cs and email-api/Program.cs
- Update cv-search-job references to use email-data project and Email.Data namespace
- Update solution file to reference new email-data project path
- Remove hardcoded schema name from SmtpEmailDispatcher, use template service instead

This maintains consistency with other data project naming convention (no service-type suffix).
All tests passing, build succeeds.

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

Apis/api/Program.cs

@@ -1,10 +1,10 @@
 using System.Reflection;
 using Api.Services;
 using Api.Services.Contracts;
-using EmailApi.Data;
-using EmailApi.Data.Repositories;
-using EmailApi.Data.Repositories.Contracts;
-using EmailApi.Data.Services;
+using Email.Data;
+using Email.Data.Repositories;
+using Email.Data.Repositories.Contracts;
+using Email.Data.Services;
 using EmailApi.Models.Clients;
 using EmailApi.Models.Settings;
 using Microsoft.EntityFrameworkCore;
@@ -57,7 +57,7 @@ try
         options.UseSqlServer(connectionString, sql =>
         {
             sql.MigrationsHistoryTable(EmailApiDbContext.MigrationTableName, EmailApiDbContext.SchemaName);
-            sql.MigrationsAssembly("email-api-data");
+            sql.MigrationsAssembly("email-data");
         });
     });