chore: remove all tabs & trailing spaces from SQL files

[kbsali]

What kind of change does this PR introduce?

docs update

What is the current behavior?

When dumping an entire project, the SQL sometimes has tabs instead of 2 spaces (which seems the default)

What is the new behavior?

Additional context

[coveralls]

Pull Request Test Coverage Report for Build 3572813994

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 390 unchanged lines in 15 files lost coverage.
• Overall coverage decreased (-2.8%) to 54.923%

---

Files with Coverage Reduction	New Missed Lines	%
internal/db/branch/switch_/switch_.go	1	96.61%
internal/db/diff/migra.go	2	98.81%
internal/utils/docker.go	2	66.79%
cmd/migration.go	3	64.71%
internal/db/reset/reset.go	6	84.17%
cmd/projects.go	8	18.56%
internal/link/link.go	11	28.57%
internal/db/start/start.go	13	64.62%
cmd/link.go	14	25.0%
internal/db/lint/lint.go	20	78.79%

Totals
Change from base Build 3612839365:	-2.8%
Covered Lines:	3057
Relevant Lines:	5566

---

💛 - Coveralls

[sweatybridge]

When dumping an entire project, the SQL sometimes has tabs

@kbsali are you referring to running pg_dump on your local dev database? If so, that is out of scope for CLI. What we do support is dumping remote project with db remote commit.

That said, we are looking into generating these initial schemas in a fully automated way. So our preference is to fix the schemas in the respective services upstream. In this case, it is supabase/auth#843.

[kbsali]

ok, perfect. I wasn't sure how these sql files were generated.
That being said, there are more pieces of SQL with "wrong" indent types like storage.extension... where is that coming from ? (not Gotrue as far as I can see)

[sweatybridge]

Probably from either of these repos

• https://github.com/supabase/storage-api/tree/master/migrations/tenant
• https://github.com/supabase/postgres/tree/develop/migrations