ENG-794 - Added a new script "check-schema" to replace old check-types (#382)

* - Added a new script "check-schema"  to replace old check-types
- Updated README.md to reflect the new "check-schema" command,

* rm formatting

* Update "check-schema" script in package.json to use tsx for linting instead of npm run lint, improving consistency in script execution.

Author: mdroidian

packages/database/README.md

@@ -26,7 +26,7 @@ We follow the Supabase [Declarative Database Schema](https://supabase.com/docs/g
 1. Assuming you're working on a feature branch.
 2. Make changes to the schema, by editing files in `packages/database/supabase/schemas`
 3. If you created a new schema file, make sure to add it to `[db.migrations] schema_paths` in `packages/database/supabase/config.toml`. Schema files are applied in that order, you may need to be strategic in placing your file.
-4. `turbo check-types`, which will do the following:
+4. `turbo check-schema`, which will do the following:
     1. Check your logic with `sqruff lint supabase/schemas`
         1. If there are errors there, you can fix them with `npm run lint:fix`
     2. Stop Supabase.

packages/database/package.json

@@ -15,6 +15,7 @@
     "dev": "supabase start && tsx scripts/createEnv.ts && supabase functions serve",
     "stop": "supabase stop",
     "check-types": "tsc --noEmit --skipLibCheck",
+    "check-schema": "tsx scripts/lint.ts && supabase stop && npm run dbdiff",
     "lint": "eslint . && tsx scripts/lint.ts",
     "lint:fix": "tsx scripts/lint.ts -f",
     "build": "tsx scripts/build.ts && npm run genenv -- local",