Kit bugfixes

[L-Mario564]

Addresses 19 bugs:

#3254
bit data type in PG generated with quotes around it. Not anymore.

#2630
Added a proper migration strategy when altering a serial column to a integer generated always as identity column in PG.

Before:

ALTER TABLE "table" ALTER COLUMN "id" SET DATA TYPE integer;
ALTER TABLE "table" ALTER COLUMN "id" ADD GENERATED ALWAYS AS IDENTITY (sequence name "table"."table_id_seq" INCREMENT BY 1 MINVALUE 1 MAXVALUE 2147483647 START WITH 1 CACHE 1);

Now:

ALTER TABLE "table" ALTER COLUMN "id" DROP DEFAULT;
DROP SEQUENCE "table_id_seq";
ALTER TABLE "table" ALTER COLUMN "id" ADD GENERATED ALWAYS AS IDENTITY (sequence name "table_id_seq" INCREMENT BY 1 MINVALUE 1 MAXVALUE 2147483647 START WITH 1 CACHE 1);
SELECT setval(pg_get_serial_sequence('table', 'id'), coalesce(max("id"), 0) + 1, false) FROM "table";

#3004
The value for maxvalue for the created sequence when using bigint data type was incorrect. This is now the real 64-bit integer limit.

#3713
Check constraints didn't insert parameterized values.

check('name', sql`${table.age} > ${21}`);

Before:

... CHECK ("users"."age" > $1);

Now:

... CHECK ("users"."age" > 21);

#3867
In the issue reported, the user had a .DS_Store file that Drizzle was attempting to read as a JSON file. Added the extra check to the internal prepareOutFolder function to only include .json files.

#3795
This doesn't seem to be a bug present in latest. I added tests to confirm this.

#3609
Default value for bigint data type wasn't handled properly, leading to an error when attempting to JSON.stringify it.

#3679 & #3820
Using an non-alphanumeric character within a sequence's name (like a "-") would result in changes being applied when there weren't any. This is now fixed.

#3347, #2806, #3685 & #2454
Fixed issues with geometry(point) serialization:
1- geometry(point) got instrospected as geometry(Point).
2- Default value was serialized as [Object object].

#3884
Prevent type error when the table belonging to a check constraint wasn't found during introspection in MySQL.

#3585
This seems to have been fixed in newer versions of Kit. Added a test to verify such.

#3559 & #3549
Empty strings upon introspection are now handled correctly.

#1680
Fixed in latest. Added test to verify.

#2888
Composite unique constraint got recreated in Postgres even if the column order hasn't been modified. Fixed by retrieving the order of the constraint's columns upon introspection.