[SQLite] fixing a bug in creating table with autoInc column and custom primarykey

[hfazai]

Creating a table that has an autoIncrement column and a custom primarykey (that contains single column) causes an error in SQLite dialect. Here is an example :

object Test : Table("Test") {
        val id = integer("id").autoIncrement()

        // Rest of columns

        override val primaryKey = PrimaryKey(id, name = "PKConstraintName")
    }

SQL generated :

CREATE TABLE IF NOT EXISTS Test(id INTEGER PRIMARY KEY AUTOINCREMENT, CONSTRAINT PKConstraintName PRIMARY KEY (id))

Error : SQL error or missing database (table "Test" has more than one primary key)

.

=> So in this PR I did a little change to consider this case.

[hfazai]

When using SQLite : If isOneColumnPK() = true and the column type is integerAutoincType, then colType.sqlType() returns : "INTEGER PRIMARY KEY AUTOINCREMENT" at the same time when defining a costom primaryKey name, a primary key constraint is generated too. That's why we get the error.
Here I added a condition to prevent defining primary key multiple times.