[FLINK-39210][table] Fixed Memory Leak Issue in Flink SQL with Multiple Temporal Joins

[Au-Miner]

What is the purpose of the change

Fix Memory Leak Issue in Flink SQL with Multiple Temporal Joins.

Brief change log

• Clean up per-key bookkeeping (nextLeftIndex, registeredTimer) when both probe and build sides are fully drained for a key, preventing unbounded state growth in jobs without idle-state retention.
• Remove tombstoned (DELETE/UPDATE_BEFORE) versioned rows from rightState during watermark-driven cleanup, allowing the state backend to fully reclaim per-key entries for deleted versioned rows.

Verifying this change

This change is verified by new and existing tests in TemporalRowTimeJoinOperatorTest#testPerKeyStateIsCleanedUpWithoutStateRetention.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

[flinkbot]

CI report:

• 49895ae Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build