Fix flaky RestoreFromBackupAsync test: replace Progress<T> with synchronous IProgress<T>

[Copilot]

The RestoreFromBackupAsync_ValidUnencryptedBackup_RunsImportButFailsAtRelationalOnlyTallyStep test was failing non-deterministically in CI. The root cause: it used new Progress<RestoreProgress>(...), which dispatches its callback asynchronously on the ThreadPool (no SynchronizationContext in xUnit). The first progress event (RestoreStep.Validating) is reported before any await, so its callback races the test's assertion and can miss the list.

Changes

• DatabaseRestoreServiceTests.cs — replace the Progress<T> instance with SyncProgress<T>, a minimal file-scoped IProgress<T> that invokes the handler synchronously on the calling thread, making event capture deterministic:

// Before — async dispatch, racy
var progress = new Progress<RestoreProgress>(p => progressEvents.Add(p));

// After — synchronous, deterministic
IProgress<RestoreProgress> progress = new SyncProgress<RestoreProgress>(p => progressEvents.Add(p));

// Helper added at bottom of file
file sealed class SyncProgress<T>(Action<T> handler) : IProgress<T>
{
    public void Report(T value) => handler(value);
}

No production code was changed.

[github-actions]

🎉 This PR is included in version 1.2.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀