sink(ticdc): add event key output for debezium (#11649)

[ti-chi-bot]

This is an automated cherry-pick of #11649

What problem does this PR solve?

Issue Number: close #11652

What is changed and how it works?

Debezium send event key and event value to kafka. I added event key output to this PR.
Also modify function SanitizeName for keeping same with official code.

Check List

Tests

• Unit test
• Integration test

Questions

Will it cause performance regression or break compatibility?

Do you need to update user documentation, design documentation or monitoring documentation?

Release note

Fix the issue that the Key of Kafka messages has't been filled in Debezium protocol.

[codecov]

Codecov Report

Attention: Patch coverage is 26.92308% with 209 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-8.1@6cd1c19). Learn more about missing BASE report.

Additional details and impacted files

Components	Coverage Δ
cdc	61.6084% <0.0000%> (?)
dm	51.0953% <0.0000%> (?)
engine	63.4444% <0.0000%> (?)

Flag	Coverage Δ
unit	57.3495% <26.9230%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

@@               Coverage Diff                @@
##             release-8.1     #11965   +/-   ##
================================================
  Coverage               ?   57.3495%           
================================================
  Files                  ?        854           
  Lines                  ?     126320           
  Branches               ?          0           
================================================
  Hits                   ?      72444           
  Misses                 ?      48454           
  Partials               ?       5422           

[ti-chi-bot]

@ti-chi-bot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
jenkins-ticdc/verify	4691d09	link	true	/test verify

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[wk989898]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wk989898

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [wk989898]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment