refactor: EXPOSED-728 [SQLite] Remove ENABLE_UPDATE_DELETE_LIMIT metadata check from core function provider

[bog-walk]

Description

Summary of the change: Deprecate SQLiteDialect.ENABLE_UPDATE_DELETE_LIMIT and replace with metadata functions that perform the same query, but which can be extracted into separate modules when R2DBC is introduced.

Detailed description:

• Why:

SQLiteDialect has a companion property that sends a low-level JDBC connection query to check if LIMIT clause is allowed in either update or delete statements. The latter is only possible if SQLite is built from the source with the compile-time flag ENABLE_UPDATE_DELETE_LIMIT enabled (source docs).

In preparation for R2DBC, this query needs to be removed from exposed-core so that it can be implemented in both a blocking and non-blocking way.
FunctionProvider is not expected to have jdbc vs r2dbc versions. So the metadata check is instead placed in ExposedDatabaseMetadata and invoked in update() and delete() directly, since they will all be extracted to their respective modules.

This was missed from previous refactors because it doesn't use exec().

• How:
  • Deprecate SQLiteDialect.ENABLE_UPDATE_DELETE_LIMIT
  • Replace with DatabaseDialect.supportsLimitWithUpdateOrDelete(), which calls ExposedDatabaseMetadata.supportsLimitWithUpdateOrDelete() to send the same query with SQLite. All other dialects are hard-coded with a boolean value.
  • Remove this check from SQLiteDialect's function provider and place directly in Table.update() and Table.delete variants.

---

Type of Change

Please mark the relevant options with an "X":

• Other - refactor
• Deprecation

Affected databases:

• SQLite

Checklist

• Unit tests are in place
• The build is green (including the Detekt check)
• All public methods affected by my PR has up to date API docs

---

Related Issues

EXPOSED-728