Parse and ignore SQLite DDL conflict-clause

[lukaseder]

Starting with at least jOOQ 3.15 and #11286 (probably earlier too), we've started parsing SQLite's DDL, because the PRAGMA commands simply don't deliver enough meta data. This means that we run into limitations when users use more advanced, vendor specific features in SQLite, which we don't support yet, see e.g. this report: #13879

This issue will parse and ignore some documented SQLite DDL clauses, including:

• conflict-clause: https://www.sqlite.org/syntax/conflict-clause.html
• PRIMARY KEY [ ASC | DESC ]: https://www.sqlite.org/syntax/column-constraint.html
• MATCH: https://www.sqlite.org/syntax/foreign-key-clause.html. Should be supported formally: Add support for MATCH clause in foreign keys #10430
• [ NOT ] DEFERRABLE [ INITIALLY ( DEFERRED | IMMEDIATE ) ]: https://www.sqlite.org/syntax/foreign-key-clause.html. This was supported already in jOOQ 3.14 / Support parsing NOT DEFERRABLE INITIALLY IMMEDIATE on foreign key constraints #10360

---

See also:

• https://www.sqlite.org/lang_createtable.html
• https://www.sqlite.org/syntax/column-constraint.html
• https://www.sqlite.org/syntax/foreign-key-clause.html
• Issues with UNIQUE and ON CONFLICT after updating to 3.17.3 (SQLite) #13879

[lukaseder]

Fixed in jOOQ 3.18.0, 3.17.4 (#13888), and 3.16.10 (#13889)