[WIP] Define strategy and roadmap for Akkatecture migration

[Copilot]

Thanks for assigning this issue to me. I'm starting to work on it and will keep this PR's description up to date as I form a plan and make progress.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>1. Akkatecture Migration: Planning & Roadmap</issue_title>
<issue_description>Define the overall strategy and phased roadmap for migrating UniVoting to an Akkatecture/actor-based, event-sourced architecture.

Tasks:

• Identify current aggregate roots and domain models.
• Propose CQRS/event sourcing mapping for existing components.
• Plan incremental migration (aggregate-by-aggregate or feature slice).
• Determine event store and projection/read model infrastructure.
• Document expected benefits and risks.
• Create a migration roadmap document (docs/migration-roadmap.md) summarizing planned phases and references.

Example content for roadmap is provided in the code scaffolding above.

This issue will serve as an epic/umbrella for migration tickets.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes 1. Akkatecture Migration: Planning & Roadmap #32

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.