feature: support sqlite contains path queries

[jiazheng2]

Checks

• Do only one thing
• Non breaking API changes
• Tested

What did this pull request do?

Support using path for SQLite JSON array contains queries.

This addresses issue #216 to some extent.

Use case description

If we have

| json_column   |
|---------------|
| {"a": [1, 2]} |

For SQLite databases, we can now do

JSONArrayQuery("json_column", "a").Contains(1)

This gets translated to

EXISTS(
    SELECT 1 FROM json_each(`json_column`, "$.a") WHERE value=1
) AND json_array_length(`json_column`, "$.a") > 0

Note the additional json_array_length check compared to the previous implementation.

This fixes the inconsistency in the behaviour between the MySQL and SQLite dialects.

Previously, if we have

| json_column |
|-------------|
| {"a": 1}    |

When we do

JSONArrayQuery("json_column").Contains(1)

The where condition is translated to

EXISTS(
    SELECT 1 FROM json_each(`json_column`) WHERE value=1
) 

This returns the row {"a": 1} because the for_each function iterates over the map as well. And
the key-value pair "a" and 1 fulfils the query criteria WHERE value=1. This behaviour is
different from the MySQL implementation.

With this change, the where condition gets translated to

EXISTS(
    SELECT 1 FROM json_each(`json_column`) WHERE value=1
) AND json_array_length(`json_column`) > 0

json_array_length for a non-array object is 0, and therefore the second where clause is false. Additionally,
any contains query should return false for an empty target array.

[jiazheng2]

@jinzhu 麻烦review一下 🙏