connector: support sinking jsonb as dynamic type

[xiangjinwu]

Is your feature request related to a problem? Please describe.

As an analogy to #10772, there are 2 styles to sink a jsonb value out:

Always as a JSON-encoded string:

• 1 -> "1"
• true -> "true"
• null -> "null"
• "foo" -> "\"foo\""
• [1, true, "foo"] -> "[1, true, \"foo\"]"
• {"k": 2} -> "{\"k\": 2}"

As different types based on jsonb_typeof:

• 1 -> 1
• true -> true
• null -> null
• "foo" -> "foo"
• [1, true, "foo"] -> [1, true, "foo"]
• {"k": 2} -> {"k": 2}

Currently the kafka sink uses the former style, because each RisingWave data type always maps to a single data type in output. But the latter form may be preferred in certain cases.

The latter style should report an error when the sink column is not dynamic type.

Describe the solution you'd like

Introduce a new sink option to switch between the 2 styles, similar to existing TimestampHandlingMode. The default can be used to retain backward compatibility.

Describe alternatives you've considered

No response

Additional context

risingwave/src/connector/src/sink/utils.rs

Lines 355 to 357 in 26edff4

	(DataType::Jsonb, ScalarRefImpl::Jsonb(jsonb_ref)) => {
	json!(jsonb_ref.to_string())
	}

cc @StrikeW @tabVersion @BugenZhao

[yuhao-su]

Do we need this for DebeziumJson?

[xiangjinwu]

Do we need this for DebeziumJson?

According to Debezium the jsonb data type is always mapped to Kafka Connect string type. It is never a dynamic type