feat: message_as_jsonb to handle circle dep in protobuf

[tabVersion]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

resolve #19915
following #18380

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

add a new field messages_as_jsonb dedicated to encode protobuf, it lists fields should be seen as jsonb type and we can leverage this to handle recursive types

for example,

message A {
  int32 int_value,
  string string_value,
}

If not set in messages_as_jsonb, the type in RW should be A struct<int_value int, string_value varchar>.
If messages_as_jsonb='some_pkg.A', the type in RW should be A jsonb.

---

When finding a recursive def in proto, we will display the circular dep relation and prevent creating the source/table.

Users can refer the error message and adding the types to messages_as_jsonb

circular reference detected: parent(recursive.ComplexRecursiveMessage.parent)->siblings(recursive.ComplexRecursiveMessage.Parent.siblings), conflict with parent(recursive.ComplexRecursiveMessage.parent), kind recursive.ComplexRecursiveMessage.Parent. Adding recursive.ComplexRecursiveMessage.Parent to "messages_as_jsonb" may help.

[xiangjinwu]

Pretty sure the PR is incomplete and untested so I converted it back to draft. You will notice the missing pieces when you start testing (in addition to the ci failure).

[xiangjinwu]

Intentional bug fix

[tabVersion]

cherry pick to release 2.1 #19992