fix: Update drizzle config to be up to date with the latest version

[gcjbr]

Closes #

✅ Checklist

• [x ] I have followed every step in the contributing guide (updated 2022-10-06).
• The PR title follows the convention we established conventional-commit
• I performed a functional test on my final commit

---

Changelog

_ drizzle-config-sqlite.ts, drizzle-config-postgres.ts and drizzle-config-mysql.ts were changed to adhere to Drizzle's format

---

Screenshots

While running Drizzle Studio we are always asked to update it to the latest version, or it won't show the UI. After tha last update, it's finding an error with the current template configs.

This fixes it.

💯

[changeset-bot]

🦋 Changeset detected

Latest commit: 7e765e7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
create-t3-app	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
create-t3-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 10, 2024 7:53pm

[vercel]

@gcjbr is attempting to deploy a commit to the t3-oss Team on Vercel.

A member of the Team first needs to authorize it.

[juliusmarminge]

Can you bump the versions in dependencyVersionMap as well just so that it will always pull ^0.21 no matter what package manager? Thanks!

[gcjbr]

Can you bump the versions in dependencyVersionMap as well just so that it will always pull ^0.21 no matter what package manager? Thanks!

Done

[juliusmarminge]

CI failing

[juliusmarminge]

Need to Bump here too https://github.com/t3-oss/create-t3-app/blob/main/cli/src/installers/dependencyVersionMap.ts

[gcjbr]

CI failing

I've bumped the dependencyVersionMap. I see the linter is failing, it's failing locally on the main branch as well, on the same places it's failing here.

Weird 👁️

[juliusmarminge]

idk why the hell shiki is overriding global Response type...

cba to dig in - just added some casts

[gcjbr]

idk why the hell shiki is overriding global Response type...

cba to dig in - just added some casts

Right?

Weirdest to me is the unchanged code is also not passing the linting. How the heel did it pass linting on main in the first place? 🥸

[juliusmarminge]

okay it was the big lockfile diff that was causing the issues

i reverted the lock file changes and resynced it and thing's are back to normal

[juliusmarminge]

idk what pnpm version you're on but you had caused like 6k lines of diff in the lockfile which i reverted b0e6dfe

[juliusmarminge]

Now we have some failing CI again (that's actually cause of the change)

Can you fix it up so it's passing?

[gcjbr]

idk what pnpm version you're on but you had caused like 6k lines of diff in the lockfile which i reverted b0e6dfe

pnpm -v
8.6.5

Nice catch, thanks!

I'll fix the other test

[gcjbr]

@juliusmarminge , done!

Can you tell me your PNPM version, btw?

Just so I don't create a mess in the future

[juliusmarminge]

I use corepack so it matches whatever is in package.json#packageManager