✨ 364 Add Vogen for Strongly Typed IDs

[danielmackay]

1. What triggered this change? (PBI link, Email Subject, conversation + reason, etc)

#364

2. What was changed?

This pull request includes several changes aimed at refactoring the codebase to use strongly typed IDs and improving the configuration of the Entity Framework Core (EF Core) models. The most important changes include the introduction of the Vogen library for value objects, updates to the HeroId, TeamId, and MissionId types, and adjustments to the entity configurations.

Refactoring to use strongly typed IDs:

• src/Domain/Heroes/Hero.cs: Replaced the HeroId struct with a Vogen value object and updated the Create method to use HeroId.From. [1] [2]
• src/Domain/Teams/Mission.cs: Replaced the MissionId struct with a Vogen value object and updated the Create method to use MissionId.From. [1] [2]
• src/Domain/Teams/Team.cs: Replaced the TeamId struct with a Vogen value object and updated the Create method to use TeamId.From. [1] [2]

Entity Framework Core configuration updates:

• src/Infrastructure/Persistence/ApplicationDbContext.cs: Added the RegisterAllInVogenEfCoreConverters method call in ConfigureConventions to register the Vogen converters.
• src/Infrastructure/Persistence/Configuration/HeroConfiguration.cs, MissionConfiguration.cs, TeamConfiguration.cs: Commented out the manual conversions for HeroId, MissionId, and TeamId as they are now handled by Vogen's EF Core converters. [1] [2] [3]

Additional changes:

• src/Domain/Domain.csproj: Added the Vogen package reference.
• tests/Domain.UnitTests/Heroes/HeroTests.cs, MissionTests.cs, TeamTests.cs: Updated tests to use the HeroId.From, MissionId.From, and TeamId.From methods. [1] [2] [3] [4]

3. Did you do pair or mob programming?

No

[AntPolkanov]

LGTM 👍