sql: use set to test results of SELECT

[Korablev77]

Currently, inside tap-tests resulting set of SELECT is checked considering order. For instance,

SELECT * FROM t1;
[1, 'a', 3] -- is OK
[1, 3, 'a'] -- is not OK

However, any insignificant change of query planner may affect choice of index to be used. Depending on index, order of resulting set produced by SELECT can change and tests become invalid.
Thus, the suggestion is to check only resulting sets (i.e. don't take into account order) where query plan is not a part of test.

[Totktonada]

@Korablev77 Are there tests where the order is matter or we can use order-unaware compare within do_execsql_test?

[Korablev77]

@Totktonada
AFAIK, without ORDER BY or GROUP BY clauses order of rows is not specified.