Schema mismatch in source can lead to cluster panic

[kwannoel]

Describe the bug

After two columns were added in the upstream source catalog in schema registry, the source started to panic.

thread 'rw-streaming' panicked at src/stream/src/executor/wrapper/schema_check.rs:48:29:
	
2024-09-25 23:06:09.896	
schema check failed on ExecutorInfo { schema: Schema { fields: [...] }, pk_indices: [34], identity: "Source 746F00002742" }: column type mismatched at position 35: expected Some(List(Varchar)), found Some("Timestamptz")

Error message/log

No response

To Reproduce

No response

Expected behavior

Should not panic.

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response

[KeXiangWang]

Some additional information. The user who encountered this issue is using a hotfix image derived from v1.9.1.

[xiangjinwu]

Sounds same as #16486/#17293 fixed since v1.10