Prevent sql tokenizer from assuming FOR is a statementType when used with data-type

[janfh]

Fixes #315

Modified fixStatement to not assign statementType for "FOR" when:

• Previous token is "closebracket"
• Token after the next is the word "DATA"

[worksofliam]

@janfh This is a great change. But, since you are making a change in a fairly critical file, it'd be nice to have a test case for this change. Might I recommend you add a test for this in src/language/sql/tests/tokens.test.ts? I would usually use the statement that you found this issue with:

select 
  cast(x'01' as char(1) for bit data) as something,
  case when 1=1 then 'makes sense' else 'what?' end as something_else
  from sysibm.sysdummy1;

Run the tests with npm run language:test.

If you need any help - let me know. I am very grateful for this PR.

[janfh]

@janfh This is a great change. But, since you are making a change in a fairly critical file, it'd be nice to have a test case for this change.

@worksofliam : I've added a test case. But please let me know if you would like something else, or feel free to adjust any of these changes :)

[worksofliam]

@janfh Looking good. I added one more additional test in a commit of my own to ensure the statement length (as this is what your code fixed). I can now merge. Thanks again!

[worksofliam]

@janfh I should mention that this should come out soon. I am trying to get some edge cases of the syntax checker done, and hopefully we can release this fix along with that.