Change liquidjs parameter parsing to use Liquid’s Tokenizer

[zachleat]

https://liquidjs.com/tutorials/parse-parameters.html#Parse-Parameters-as-Values
https://liquidjs.com/tutorials/parse-parameters.html#Parse-Key-Value-Pairs-as-Named-Parameters

Currently implementation predated those features and is using a one-off parser using moo: https://github.com/11ty/eleventy/blob/0f44f756a30247515033945e74e171a293bc75d5/src/Engines/Liquid.js

I think due to the size of this change, we’ll probably want a configuration escape hatch for folks to swap back to the old parameter parser

Excellent prior art #1263 #1733

[AleksandrHovhannisyan]

Hey, just checking to see if you're accepting help/contributions for this issue. I noticed that 11ty's Liquid engine is currently only using moo in two places:

eleventy/src/Engines/Liquid.js

Line 24 in 0f44f75

this.argLexer = moo.compile(Liquid.argumentLexerOptions);

eleventy/src/Engines/Liquid.js

Line 100 in 0f44f75

lexer = moo.compile(Liquid.argumentLexerOptions);

By size of the change, do you mean that it's high impact, or are there other changes that would need to be made as well?

[jgerigmeyer]

@zachleat Any thoughts on @AleksandrHovhannisyan's question above? Would you be interested in contributions for this issue? Thanks!