[Docs] put migrations code in a class library separate from the EF Core context

Documentation updated to recommend placing EF Core migration code in a separate class library rather than alongside the EF Core context. This change improves project organization and maintainability by separating concerns between data access logic and migration operations.