feat(cdc): add a parameter to control timeout of cdc source waiting time

[KeXiangWang]

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

What's changed and what's your intention?

In our production environment, we found one case that the upstream system's table schema was too complicated so that takes long time to fetch. The time required exceeded the preset timeout threshold in #14406 and leads to the failure of source creation. In this PR, we add a runtime parameter to control it. If a user encounter a error like this when creating cdc source:

RROR:  Failed to run the query

Caused by these errors (recent errors listed first):
  1: gRPC request to meta service failed: Internal error
  2: get error from control stream: worker node {}, gRPC request to stream service failed: Internal error: Failed to send barrier with epoch {} to actor 1: channel closed;

he can run SET cdc_source_wait_streaming_start_timeout TO 120; to increase timeout from the default 30s to 120s can recreate the source.

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

risingwavelabs/risingwave-docs#2126

[kwannoel]

Customer-facing issue, so LGTM. Best if we can add test cases for this.

e.g.

1. Add the complex catalog.
2. Show that it takes a long time and timeout occurs.

Then subsequently we can optimize this path as well without having to change timeout, since we have a repro case.

[KeXiangWang]

we can add test cases for this.

Added an issue to track. #16622

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[fuyufjh]

The error message is not clear. Let's improve it later