[FLINK-35323][runtime] Fix transform failure when one rule matches multiple tables with incompatible schema

[yuxiqian]

This closes FLINK-35323.

Currently, Transform module doesn’t support handling multiple tables with different schema within one projection / filtering rule. A minimum reproducible example is:

transform:
  - source-table: DB.TABLE\.*
    projection: \*

If there are DB.TABLE1 and DB.TABLE2 in upstream source but with different schema, transform operator will panic. This is not intended and turns out to be related to incorrectly handled processor caching strategy. Fixing the cache key should resolve this problem.

[yuxiqian]

Could @PatrickRen please take a look? Thanks!

[melin]

Table A_1 has the same schema as table A_2, but A_3 has more fields than A_1. This scenario is not supported. Added conditional judgment: