Remove Contact.Application service injection from Contact.Api Program.cs

[Copilot]

This PR removes the AddApplicationServices call from the Contact.Api project's Program.cs file as requested in the issue.

Changes Made

• Removed builder.Services.AddApplicationServices(builder.Configuration); from Program.cs
• Maintained the using Contact.Application; statement as it's still needed for AppSettings configuration
• Preserved the infrastructure services registration (AddInfrastrcutureServices)

Impact

⚠️ Breaking Change: This change removes the registration of application services from the dependency injection container, which will cause runtime failures when attempting to instantiate controllers.

Before

// Add services to the container.
builder.Services.AddInfrastrcutureServices(builder.Configuration);
builder.Services.AddApplicationServices(builder.Configuration);

After

// Add services to the container.
builder.Services.AddInfrastrcutureServices(builder.Configuration);

Runtime Behavior

• ✅ Compilation: Project builds successfully
• ✅ Application Startup: No startup errors
• ❌ API Functionality: Controllers fail to instantiate due to missing service dependencies

Example error when calling /api/users/register:

HTTP 500 - "Unable to resolve service for type 'Contact.Application.Interfaces.IUserService' while attempting to activate 'Contact.Api.Controllers.UsersController'"

Next Steps

To restore functionality, the application services will need to be registered through an alternative mechanism or architectural pattern that aligns with the desired clean architecture approach.

Fixes #18.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.