[hotfix][table] Avoid KeyedLookupJoinWrapper sending duplicate delete record for left join when state expired

[lincoln-lil]

What is the purpose of the change

This is a hotfix for FLINK-34166 (which fixes KeyedLookupJoinWrapper not sending incorrect delete message for inner join when previous lookup result is empty), it cause duplicate delete message for a left join when state expired(lack of ttl expiration case before), this pr fix the state stale logic and add corresponding tests.

Brief change log

• reserve single pad null logic for left join when process retract message
• update related tests

Verifying this change

• KeyedLookupJoinHarnessTest

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)

[flinkbot]

CI report:

• 3df653a Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

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

[luoyuxia]

@lincoln-lil Thanks for the pr. LGTM