ORM minor enhancements and bugfixes

[L-Mario564]

This PR aims to address many smaller issues.

• [BUG]: #1826
  Expressions like isNull, eq, etc. now output SQL<boolean> instead of SQL<unknown>.

• [BUG]: sqliteTable 3rd parameter array type error #3326
  SQLite and MySQL now match PG's array syntax for declaring extra config.

• [BUG]: Column name not being returned as snake_case  #3094
  Introduced a new method to all dialect columns: nameWithCasing. The avoid breaking the existing name property, this method was introduced to add further flexibility with handling casing in your queries. This can be used as such:

const users = pgTable('users', {
  firstName: text()
});

users.firstName.name; // 'firstName'
users.firstName.nameWithCasing('snake_case'); // 'first_name'
users.firstName.nameWithCasing(db); // 'first_name' - The `db` instance has `casing: 'snake_case'`

• [BUG]: inserting json does not work when using sql template string #3171
  Inserting JSON using the sql operator now works as expected when using the postgres.js driver.

• [BUG]: postgres insert and generatedAlwaysAsIdentity tries to insert null value #3576
  Fixed the condition that filters out generated columns. These shouldn't be included anymore, as expected.

• [BUG]: "Insert into ... select" expects all columns #3608
  This has been fixed. insert into ... select has been internally tweaked to handle generated columns and optional fields.

• [BUG]: PgInsertValue regression in 0.36.4 #3620
  PgInsertValue now outputs the correct type.

• [BUG]: Incorrect TypeScript inference for SQLite Blob column builder #1064
  The return type definition now matches the runtime value.

• [BUG]: Incorrect type inference with multidimensional array field PostgreSQL #1028

• [BUG]: column type json array is returning unknown[] #2913
  Arrays now handle custom type definitions rather than just resolving to unknown[].

• [BUG]: Cannot use SQL.Aliased from SubQuery in GroupBy #3632
  This was only an issue with SQLite. Now fixed.

• [FEATURE]: Nullable type inference with .mapWith() #571
  mapWith method ignored the column's nullability if a column was passed as an argument. This has been fixed.

• [BUG]: Problem with the transaction #952
  Could not reproduce this issue; however, I changed the SQL generation of transaction config in MySQL so it uses sql.raw instead of sql. This should avoid the SQL statement to begin the transaction from ever being parameterized.

• [FEATURE]: column.as("alias") method #2391
  You can now very easily alias a column:

db.select({ firstName: users.firstName.as('name') }).from(users);

[L-Mario564]

#3175 will be done in a separate PR, the changes required are larger than expected.