Align email-api and page-fetcher-api namespaces to Api.* convention

Fixes inconsistency where email-api used EmailApi.* and page-fetcher-api
used PageFetcherApi.*, while cv-matcher-api and rag-api use the generic
Api.* namespace. All four API projects now follow the same pattern.

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

Apis/email-api/Controllers/EmailController.cs

@@ -1,9 +1,9 @@
+using Api.Services;
 using EmailApi.Models.Requests;
-using EmailApi.Services;
 using Microsoft.AspNetCore.Mvc;
 using Swashbuckle.AspNetCore.Annotations;
 
-namespace EmailApi.Controllers;
+namespace Api.Controllers;
 
 /// <summary>
 /// Internal email relay. Accepts an HTML body fragment from trusted callers

Apis/email-api/Program.cs

@@ -3,7 +3,7 @@ using Email.Data;
 using Email.Data.Repositories;
 using Email.Data.Repositories.Contracts;
 using Email.Data.Services;
-using EmailApi.Services;
+using Api.Services;
 using Microsoft.EntityFrameworkCore;
 using EmailApi.Models.Settings;
 using Models.Settings;

Apis/email-api/Services/SmtpEmailDispatcher.cs

@@ -7,7 +7,7 @@ using MimeKit;
 using EmailApi.Models.Settings;
 using Models.Settings;
 
-namespace EmailApi.Services;
+namespace Api.Services;
 
 /// <summary>
 /// Wraps an HTML body fragment in the branded HTML shell and sends the resulting email via SMTP using MailKit.