chore: style sql

[chris13524]

Description

Make SQL style consistent. While it's generally a bad idea to change existing migrations, these should be functionally equivalent and won't be rerun anyway because the migration ID is what determines if the migration was already run or not.

This PR matches notify-server styling and has a companion PR here.

This style matches what I've generally seen in the Postgres documentation:

• lowercase type names
• capital constraint names (sometimes I see lowercase, but uppercase seems more common)
• capital ARRAY
• opening parenthesis on same line
• 4 space indents
• space between the constraint name and the columns it applies to e.g. UNIQUE (device_token)

Also as a personal preference:

• no IF NOT EXISTS for table creation as these are migrations, and shouldn't exist anyway (and if they do, there is a potential for being out of sync)
• generally have newlines between each statement
• trailing newlines at end of file

How Has This Been Tested?

Not tested

Due Diligence

• Breaking change
• Requires a documentation update
• Requires a e2e/integration test update

[arein]

Sweet - FYI in other repos we use sqlfluff for this - it's an awesome tool

[chris13524]

@arein nice! We should pull in something like this. Would be nice if it had a brew install though