Since #10164, we have ConfigureAwait(false) everywhere; this can cause issues in certain data binding scenarios, when accepting changes triggers a UI change, which is no longer executed on the UI thread (e.g. #22841).

We could specifically use ConfigureAwait(true) in the code path leading to AcceptAllChanges (specifically in two places: DbContext.SaveChangesAsync, StateManager.SaveChangesAsync).