Invalid parsing of legacy query strings

[bart-degreed]

In earlier versions, JADNC allowed the next query string:

?filter[title]=like:First,like:Second

which would only match titles containing both words "First" and "Second". We then took a breaking change to compose multiple filters using OR instead of AND for json:api compliance. Taking that into account, using the new syntax this is equivalent to:

?filter=expr:or(contains(title,'First'),contains(title,'Second'))

The bugs is that when legacy query string syntax is enabled, the parser fails to convert this correctly. It does not raise an error, but produces:

?filter=contains(title,'First,like:Second')

which is wrong.