[INLONG-11537][Sort] Optimize the session key generation of TubeMQ Source

[vernedeng]

Fixes #11537

Motivation

Optimize the session key generation of TubeMQ Source

Modifications

The original way to generate a session key is to combine the job id with the base session key, which leads to data loss in the case of flink failover with only one task restart due to the reuse of the same session key.

The more reasonable way is to find a unique key different from the former one after each failover.

Verifying this change

(Please pick either of the following options)

• This change is a trivial rework/code cleanup without any test coverage.

• This change is already covered by existing tests, such as:
  (please describe tests)

• This change added tests and can be verified as follows:

  (example:)

  • Added integration tests for end-to-end deployment with large payloads (10MB)
  • Extended integration test for recovery after broker failure

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
• If a feature is not applicable for documentation, explain why?
• If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation