feat: Make goose annotations case-insensitive

[obalunenko]

This PR does two things:

• Add support for case-insensitive annotations Make goose annotations case-insensitive #678
• Add annotations validations
• Improve space sanitation in statements comments Document "SQL migration file: must start with '-- +goose Up'" (and not goose Down) #163

Closes #678

[obalunenko]

@mfridman please take a look, when you have a chance

[obalunenko]

@mfridman, Could you please run the pipeline? I fixed linter warning

[mfridman]

Thanks for putting this together, I'll try my best to get a review within a week.

[mfridman]

I've been going back and forth on whether we should do this.

I.e., a goose annotation must begin with -- +goose, with no leading white space.

If we do, we'll need to update the blog (I want to move some of this "blog" content into formal docs)

https://pressly.github.io/goose/blog/2022/overview-sql-file/#quick-start

[obalunenko]

I can remove this line and add a check if the line has a leading space and throw an appropriate error.

[mfridman]

That's probably the right thing:

1. Only allow -- +goose <annotation> without leading space
2. Raise an error if we detect a -- +goose annotation with leading whitespace like \s+-- \+goose

[obalunenko]

I'll add changes to cover this logic

[obalunenko]

@mfridman I refactored PR to allow annotations only without leading whitespace

[mfridman]

lgtm. 🎉

[obalunenko]

@mfridman Thank you for your review!
Unfortunately, I don't have write access to this repository to merge my PR