fix(json): proper encoding for json array

[SpencerTorres]

Summary

JSON is one of the few column types that implement a prefix. This change implements the StateEncoder and StateDecoder interfaces for ColJSONStr, enabling proper encoding of the column prefix.

Checklist

• Unit and integration tests covering the common scenarios were added

[ernado]

Btw when we can add a e2e test for this?

[SpencerTorres]

@ernado Do you have an example of an e2e test in this repo? I see some files referencing it, but nothing similar to what we have in clickhouse-go. If there's another column I can copy then I'll add one asap

[ernado]

Of cousre, something like

ch-go/query_test.go

Lines 420 to 435 in d7f188d

	t.Run("SelectStr", func(t *testing.T) {
	t.Parallel()
	// Select single string row.
	var data proto.ColStr
	require.NoError(t, Conn(t).Do(ctx, Query{
	Body: "SELECT 'foo' AS s",
	Result: proto.Results{
	{
	Name: "s",
	Data: &data,
	},
	},
	}))
	require.Equal(t, 1, data.Rows())
	require.Equal(t, "foo", data.First())
	})

Basically, everything that calls github.com/ClickHouse/ch-go/cht.

Also,

ch-go/client_test.go

Lines 50 to 54 in d7f188d

	func SkipNoFeature(t *testing.T, client *Client, feature proto.Feature) {
	if !client.ServerInfo().Has(feature) {
	t.Skipf("Skipping (feature %q not supported)", feature)
	}
	}

May be helpfull. If we know the protocol version starting from which we can test this JSON field.

[SpencerTorres]

@ernado thanks for the examples! I'll be sure to update these tests in the future as needed. Here's the PR for the e2e tests: #1044