ParserCLI shouldn't be so newline sensitive for procedural logic

When translating procedural logic with ParserCLI, or statement batches containing ;, currently the ParserCLI behaviour is quite inconvenient as can be seen here:

Any ; character is interpreted as a delimiter, leading to parser errors. Solutions:

• Implement DELIMITER and hint at how this works in the error message (e.g. DELIMITER // as in MySQL)
• Improve the parser to recognise ; semantics

Perhaps this is just a simple bug. Let's investigate.

Start by reproducing the procedural-logic or semicolon-containing statement batch through ParserCLI, using the example in the issue. Inspect how ParserCLI handles delimiters and parser errors, then determine whether delimiter support or improved semicolon recognition is appropriate. Done means procedural batches parse without errors and the error message explains any required delimiter syntax.