Fix :auto for multistatement queries

[OskarDamkjaer]

Multistatements with :auto would get ignored since they were not in the list of allowed multistatement commands. Preview @ http://fix_auto_multlistatement.surge.sh

This query can be used to verify that the fix works (given at least two nodes in the db it creates two nodes with label Test). Make sure you've got multistatments enabled (setting in the sidebar)

:auto MATCH (n)
WITH n
LIMIT 1
CREATE (t:Test {zid: id(n)})
RETURN t;
:auto MATCH (n)
WITH n
SKIP 1
LIMIT 1
CREATE (t:Test {zid: id(n)})
RETURN t;

The customer who reported the issue also tested it in production for the issue they ran into and confirmed the solution.

[jharris4]

This appears to fix at least the basic use cases, so was there anything we want to do to test that it works for any more complicated cases?

[OskarDamkjaer]

I've tried a few different queries I got from Greg, and the customer has supposedly tested all the cases they care about. This change doesn't change how we parse the input from the user, only changes what of the parsed commands are allowed to run, so there's no risk of introducing new syntax errors

[jharris4]

Thanks for the update. Should we add some e2e tests for auto with single & multi-statement though?

[OskarDamkjaer]

Single statement :auto is tested in loadcsv.spec.ts, I'll add a test for multi-statement :auto as well

[jharris4]

Thanks for adding the multi-statement test, LGTM