Correct handling of journal mode changes

Bug: 287126569

The SQLite database configuration is updated in a three-step process:
 1. Identify the aspects that have changed by comparing the input
    configuration to the stored configuration.
 2. Update the stored configuration.
 3. Apply the stored configuration for every aspect that changed.

The journal mode and sync mode did not follow this process.  Both
tried to identify a change to the aspect after step 2, which means
that it always detected a "no change" case (after step 2, the stored
configuration is identical to the input configuration).

This change computes the "journal mode changed" flag and the "sync
mode changed" before step 2.

Test: atest
 * CtsDatabaseTestCases
 * FrameworksCoreTests:android.database.sqlite

Change-Id: I64fb7867c2572ba9dc527335f56b93497f047c09