Dispatch notifyChange() after ending transaction.

We've received reports that immediately calling query() after hearing
a ContentObserver.onChange() may see stale data, possibly due to
WAL being enabled by default.  To resolve this, only send change
notifications after the transaction has actually ended.

Bug: 147778656
Test: atest --test-mapping packages/providers/MediaProvider
Change-Id: I50ef2feb9ea5c23567cc11ee86fa10e3f9c1ad64
1 file changed