Schema builder primary() with options object having constraintName generates incorrect sql

[hannta]

Environment

Knex version: 2.0.0
Database + version: MariaDB 10.3.34
OS: Windows 11

Bug

Using schema builder primary() with options object having constraintName results incorrect sql.

Example:

await knex.schema.createTable('my_table', (table) => {
  table.string('column_a', 10).notNullable();
  table.string('column_b', 10).notNullable();
  table.primary(['column_a', 'column_b'], { constraintName: 'my_constraint' });
});

This gives error:

Error: create table `my_table` (`column_a` varchar(10) not null, `column_b` varchar(10) not null, constraint `my_constraint` as `constraintName` primary key (`column_a`, `column_b`)) default character set utf8mb4 - You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'as `constraintName` primary key (`column_a`, `column_b`)) default character s...' at line 1

If primary() is used giving constraint name as second parameter in plain string (table.primary(['column_a', 'column_b'], 'my_constraint')) this works. Though this is deprecated way of using the primary() at least based on TS typings.

This bug was introduced in knex version 1.0.3, I suspect this pr has the root cause #5017