fix: make type-imports autofixable & general project cleanup

[juliusmarminge]

Closes #1173
Closes #1163 (disabled cache job - not optimal but not the end of the world, can make a separate package if we really want it cached)
Closes #1182
Closes #1181

✅ Checklist

• 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

Ended up being a bit of everything pr 😮‍💨

• fixes some linting, formatting, stylistic changes

[Short description of what has changed]

CleanShot.2023-02-18.at.22.22.54.mp4

---

Screenshots

[Screenshots]

💯

[changeset-bot]

🦋 Changeset detected

Latest commit: 64daf93

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
create-t3-app	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Feb 19, 2023 at 10:58AM (UTC)

[github-actions]

Running Lighthouse audit...

[c-ehrlich]

we currently use import type { foo } from "bar" in some places and import { type foo } from "bar" in others

is it worth making that consistent?

[juliusmarminge]

we currently use import type { foo } from "bar" in some places and import { type foo } from "bar" in others

is it worth making that consistent?

probably - this lint rule is gonna prefer the inline one but it doesn't complain about the other way. maybe there is a way to do that 🤔

[github-actions]

Hey t3-oss/translators!

This PR contains changes to your language. Please review the changes ❤️.

[juliusmarminge]

we currently use import type { foo } from "bar" in some places and import { type foo } from "bar" in others

is it worth making that consistent?

Done using this rule: https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/consistent-type-specifier-style.md