[magnusp]

Closes #38. Part of #54.

What changed

• LibsqlResultSetMetaData.isAutoIncrement no longer scans the whole CREATE TABLE text for the word AUTOINCREMENT. It now checks the definition of the matching column.
• Added a reusable package-private helper, LibsqlResultSetMetaData.isAutoIncrementColumn(String createSql, String columnName), so DatabaseMetaData.getColumns reports wrong types and sizes #42 can reuse the detection for getColumns instead of reimplementing the parsing.
• The helper tokenizes the CREATE TABLE statement, skipping comments, string literals, and quoted identifiers, splits the table body into column and table constraint definitions, and looks for an unquoted AUTOINCREMENT keyword in the matching column definition or table-level PRIMARY KEY (column AUTOINCREMENT) constraint.
• Added behavior tests for a column named myautoincrement, a table-level PRIMARY KEY (id AUTOINCREMENT) constraint, and a quoted identifier named AUTOINCREMENT. The existing real-AUTOINCREMENT, comment, and string-literal tests remain.

Contract decision

Parity with xerial 3.53.4.0. Probed xerial 3.53.4.0 directly for the cases below:

DDL	xerial isAutoIncrement
create table t(myautoincrement integer primary key)	false
create table t(id integer primary key autoincrement)	true
create table t(id integer primary key /* AUTOINCREMENT */)	false
create table t(id integer primary key, note text default 'AUTOINCREMENT')	false
create table t(id integer, primary key(id autoincrement))	true
create table t("AUTOINCREMENT" integer primary key)	false

The fix matches all six.

Evidence

Failing before the fix (new test on f38bd24):

[ERROR] LibsqlResultSetMetaDataTest.doesNotReportAutoIncrementForColumnNamedAutoincrement:101
Expecting value to be false but was true
[ERROR] Tests run: 9, Failures: 1, Errors: 0, Skipped: 0

Passing after the fix:

./mvnw -pl libsql-jdbc -am test
[INFO] Tests run: 39, Failures: 0, Errors: 0, Skipped: 0
[INFO] BUILD SUCCESS

./mvnw spotless:check
(no output; exit 0)

Deviations

• Base branch: this PR targets feat/jdbc-xerial-conformance (PR feat(jdbc): add xerial conformance suite and harden metadata #28) instead of main. The code this issue references (isAutoIncrement scanning CREATE TABLE, SqlTableReference) exists only on that branch; origin/main still hardcodes isAutoIncrement to false and has no table context. Implementing isAutoIncrement false-positives on identifiers containing AUTOINCREMENT #38 directly on main would require editing LibsqlResultSet.java (Lane A) and duplicating feat(jdbc): add xerial conformance suite and harden metadata #28. GitHub will retarget this PR to main when feat(jdbc): add xerial conformance suite and harden metadata #28 merges.
• No transport or sqld behavior deviation.