Stabilize logger-based unit tests by enabling fake ILogger in affected suites

[Copilot]

Recent test failures were caused by log assertions expecting ILogger.Log(...) calls that never fired. The suites were exercising LoggerMessage-generated logging paths, which now gate emission behind ILogger.IsEnabled(...).

• Root cause addressed

  • Several tests asserted warning/critical log events via FakeItEasy without configuring the fake logger’s IsEnabled behavior.
  • As a result, only IsEnabled(level) was invoked and log assertions failed.

• Test setup updates

  • Added explicit logger enablement in affected test constructors so log emission paths are exercised.
  • Updated suites include:
    • MigratorTests
    • InvitationEventConsumerTests
    • EmailUserNotificationsTests

• Behavioral impact

  • No production/runtime logic changes.
  • Test intent remains the same; only fixture setup now matches current logging semantics.

A.CallTo(() => log.IsEnabled(A<LogLevel>._))
    .Returns(true);