[Fix] [Mongo-cdc] Fallback to timestamp startup mode when resume token has expired

[jw-itq]

Purpose of this pull request

Synchronize the Flink-CDC code to fix the Mongo-CDC issue.

When MongoDB CDC connector tries to create cursor with an expired resuming token during stream task fetching stage, it will crash with a fatal exception: error due to Command failed with error 280 (ChangeStreamFatalError): cannot resume stream; the resume token was not found.

This PR added fallback logic to create cursor with timestamp, which only runs when:

Mongo CDC is in StreamTaskFetch stage
a ChangeStreamFatalError (280) is raised
Current ChangeStreamOffset has a valid timestamp field

Does this PR introduce any user-facing change?

How was this patch tested?

Check list

• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
• If you are contributing the connector code, please check that the following files are updated:
  1. Update plugin-mapping.properties and add new connector information in it
  2. Update the pom file of seatunnel-dist
  3. Add ci label in label-scope-conf
  4. Add e2e testcase in seatunnel-e2e
  5. Update connector plugin_config
• Update the release-note.

[Hisoka-X]

Thanks @jw-itq , Do we have some way to add test case verify it?

[jw-itq]

Thanks @jw-itq , Do we have some way to add test case verify it?

ok, I'll give it a try. It might take some time.

[jw-itq]

This PR also fixes the issue where MongoDB CDC fails to resume from the savepoint during restart recovery.