Consecutive semicolons cause parse errors and should be detected by a new rule ST12

Consecutive semicolons cause parse errors and should be detected by a new rule ST12: a task in LegoFlow-SWE (Harbor dataset). When linting a T‑SQL file that contains consecutive semicolons (e.g. ;; or ; ; ), SQLFluff produces an “unparsable section” error covering the entire block. This makes…