Remove `container.ts` (legacy DI) and adopt module-scoped factories

[Villarley]

🗂️ Issue: Remove container.ts (legacy DI) and adopt module-scoped factories

Description

There is a legacy container.ts (global DI container) that conflicts with the current modular architecture. Global containers hide dependencies, complicate tests, and break tree-shaking.

What is expected

• Remove container.ts and any global container registrations.
• Introduce module-scoped factories (simple functions) to compose controllers/use-cases/repositories explicitly.
• Update imports at app bootstrap to use these factories.
• Tests updated to instantiate modules without global side effects.

What should be modified

• Delete container.ts and its references.
• For each module, add a factory.ts (or similar) that wires repository → use-cases → controller(s).
• Update routers to import controller handlers from the module factory.

Tests

• Ensure unit/integration tests create module instances via factories (no global container).
• Verify parallel test runs don’t share state.

Acceptance criteria

• container.ts removed from the codebase.
• All modules compose via local factories.
• App boots and routes work as before.
• Tests pass without global DI.

Rollback plan

• Keep a branch/tag before removal.
• If needed, temporarily keep a minimal shim that proxies to module factories while all imports are updated.

[DennisRojass]

I'm eager to tackle this issue because I strongly believe in explicit, modular architecture. Global DI containers hide dependencies and create testing headaches. Replacing it with clean, module-scoped factories will immediately improve code clarity and maintainability.

My plan is straightforward: First, I'll analyze the current container to understand all dependencies. I'll then create a factory pattern for one module as a template. Each subsequent module will be migrated incrementally, with tests updated to use the new factories to ensure isolation. I'll verify the app boots correctly at each step. Finally, I'll remove container.ts completely once everything is migrated. I'll work in a dedicated branch and follow the rollback plan to ensure a safe transition.