Report multiple in-process primary connections

This adds dumpsys and logcat reporting for multiple primary
connections to a single database file.  Multiple primary connections
are not bad by themselves but misuse can lead to SQLITE_BUSY
failures. These changes are meant to simplify debugging the
SQLITE_BUSY failures.

If any database file is opened more than once (concurrently) then the
dumpsys output contains the following text:

    Concurrently opened database files
      <list of files>

If no database files were opened concurrently then the dumpsys output
does not contain the specified block.

This change only detects multiple primary connections in a single
process.

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

Bug: 309135899

Change-Id: I6550c4a0d6ff0785f67bd9d7d539c1ac52828b87