bug(mysql-cdc-source): correctly propagate errors to frontend session

[fuyufjh]

Describe the bug

When the user creates a MySQL CDC table but failed, the actual cause of failure was not propagated to the frontend session.

The users can see:

ERROR:  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;

But the actual cause must be found from logs.

We have met multiple related case reported recently, including:

• feat(cdc): add a parameter to control timeout of cdc source waiting time #16598
• Slack message
• Slack message

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response

[StrikeW]

Fixed by #17672