Add API support for sqlite3_set_authorizer().

Authorizers can be consulted during compilation of a SQL statement
to determine if each action requested by the SQL statement is allowed.

This can be useful to dynamically block interaction with private,
internal, or otherwise sensitive columns or tables inside a database,
such as when compiling an untrusted SQL statement.

This change adds the ability for developers to provide a custom
authorizer on a per-statement basis.  Since statements using a custom
authorizer are typically untrusted SQL, they're likely to have low
cache hit ratios, so we don't attempt to cache compiled statements.

Upstream SQLite is likely to continue adding new actions over
time, so our API design is a simple mirror of the underlying
callback.  Mapping of this underlying callback into higher-level
concepts is left to a Jetpack library.

Bug: 231636192
Test: atest CtsDatabaseTestCases
Change-Id: I06fa30e30c58961c9b05628e576a6f5f80fdf550