wrong JSON key classification

[galsalomon66]

-- some JSON processing identifies key-value as key-object or key-array,
this wrong identification may cause wrong results

-- wrong initialization of the JSON parser engine had caused missing a projection-key-path upon using different combinations of the from-clause path.

-- a fix for copy-constructor, upon a JSON value is an empty string, it causes a wrong result.

-- modification for JSON star operation, the new-type container saves only unique keys, to avoid high memory consumption.

-- the from-clause can handle a wild-card. i.e. upon wild-card(*) it skips the corresponding part in projection-key-path.

-- key-path may include meta-char(like a dot) select _1."i.e."[0] the "i.e." is part of the key-path.
a key-path

TODO :

{
  "array": [
    {
      "classname2": [
        {
          "a": "a_value"
        }
      ],
      "classname3": [
        {
          "a": "a_value_classname3"
        }
      ]
    }
  ]
}

the following statement returns the wrong result
select _1.array.classname2.a from s3object[*];

TODO: from-clause may point on array, _1 may scan array-values

https://bugzilla.redhat.com/show_bug.cgi?id=2242089
[s3select][json]: some of the "from" clause filters with "limit 1" are taking time as if to query the entire object and results are also incorrect