Eng-521 repair and modernize eslint with flat config

[maparent]

We have an issue with turbo lint not working well, not linting all subprojects, and not using our eslint settings.
This PR is mostly a modernization of our eslint configuration, with new flat configs.
I have also updated prettier, and made sure all packages were using the same version of typescript.
Then, this did not work as well in vscode, so I had to be more more explicit about subprojects.
It was subsequently aligned with a fresh turbo repo (from npx create-turbo@latest) and the differences were minimized, while still maintaining a functional turbo build / dev / lint.

Summary by CodeRabbit

• New Features

  • Introduced new ESLint and TypeScript lint configuration files for improved code linting consistency across multiple projects.
  • Added a multi-root workspace configuration for easier project management.

• Chores

  • Migrated ESLint configurations to the new flat config format and updated related settings.
  • Updated and streamlined TypeScript configuration files for better project structure and exclusion of build directories.
  • Revised and upgraded various development dependencies for ESLint, Prettier, and TypeScript.
  • Updated lint scripts and relaxed lint warning limits in some packages.
  • Removed deprecated or redundant configuration files.

[linear]

ENG-521 Modernize ESLint setup

[supabase]

This pull request has been ignored for the connected project plzkmulvmuhdpcmnyrhm because there are no changes detected in projects/database/supabase/supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[mdroidian]

I am nervous about removing these settings as they were inherited from the original Query Builder and have sweeping ramifications to compile, build, and dev.

I ran a few local and manual tests, so far everything seems to check out, so I won't block on this.

[mdroidian]

@maparent it looks like apps/roam/package-lock.json was moved to apps/website/package-lock.json somehow in this PR.

EDIT: reverted in #290