Consistent field naming in drizzle adapter

[tysonzero]

Goals

Have consistent field naming in the drizzle adapter

Non-Goals

No response

Background

Inconsistent field naming is unpleasant and decreases confidence in a project.

Proposal

The following should not have a seemingly random mixture of snake_case and camelCase.

const accountsTable =
    schema.accountsTable ??
    (pgTable(
      "account",
      {
        userId: text("userId")
          .notNull()
          .references(() => usersTable.id, { onDelete: "cascade" }),
        type: text("type").$type<AdapterAccountType>().notNull(),
        provider: text("provider").notNull(),
        providerAccountId: text("providerAccountId").notNull(),
        refresh_token: text("refresh_token"),
        access_token: text("access_token"),
        expires_at: integer("expires_at"),
        token_type: text("token_type"),
        scope: text("scope"),
        id_token: text("id_token"),
        session_state: text("session_state"),
      },
      (account) => ({
        compositePk: primaryKey({
          columns: [account.provider, account.providerAccountId],
        }),
      })
    ) satisfies DefaultPostgresAccountsTable)

The actual end result is quite easy to obtain and I'd be happy to do, however how the community would want to avoid breakage in existing projects is unclear to me.