[FEATURE]: Add more flexible typing for usage with exactOptionalPropertyTypes

[fnimick]

Describe what you want

When exactOptionalPropertyTypes is set in tsconfig, passing undefined to an optional property that does not explicitly allow undefined now becomes a type error.

Drizzle currently treats unset properties and properties with undefined keys the same in e.g. value objects, but the generated type for the argument to e.g. a .values() or a .set() only allows unset types, not optional ones.

Having looked at only the postgres core, I believe that .set() can be resolve by marking the optional properties as allowing undefined as well in https://github.com/drizzle-team/drizzle-orm/blob/main/drizzle-orm/src/pg-core/query-builders/update.ts#L32
and that .values() can be resolved by marking optional properties as allowing undefined as well in https://github.com/drizzle-team/drizzle-orm/blob/main/drizzle-orm/src/table.ts#L175

[AndriiSherman]

Fixed in drizzle-orm@0.38.1