Types Mismatch for postgres scalar lists

Describe the bug

nullable columns reported as non nullable

To Reproduce

docker compose up to start postgres
npm install && npx prisma migrate dev && npx prisma db seed
npm run dev to start the next app

Expected behavior

Expected Generated Types for scalar lists such as text[] integer[] json[] to be nullable

Model Definition

...

generator kysely {
  provider = "prisma-kysely"
}

...

model TestModel {
  id Int @id @default(autoincrement())

  list1 String[]
  list2 Int[]
  list3 Json[]
}

Postgres schema inspected after running prisma migrations

Versions:

@prisma/client: ^5.12.1
kysely: ^0.27.3
next: 14.2.2
prisma-extension-kysely: ^2.1.0

Additional context

Noticed this bug when my website crashed in prod, I was able to reproduce this bug pretty easily and I don't think its a prisma/prisma-keysely version issue.

I have two api's that I'm calling which do almost the same query but one is through prisma the other one is through prisma-kysely

prisma.testModel.findFirst();

prisma.$kysely
    .selectFrom("TestModel")
    .selectAll()
    .limit(1)
    .execute();

and here's what the result looks like:

prisma select

{
"id": 1,
"list1": [],
"list2": [],
"list3": []
}

prisma-kysely select
```
{
"id": 1,
"list1": null,
"list2": null,
"list3": null
}
```
and here's what the reported types look like:
prisma select
prisma-kysely select

You can find the api endpoints at /api/test and /api/test-kysely in my example repo. please follow the setup instructions mentioned in the "To Reproduce" section.

If someone can point me in the right direction I will be more than happy to dig into this and hopefully create a PR to solve this in the near future

eoin-obrien / prisma-extension-kysely