pkg/config(ticdc): hide fields that are not required for specific protocols (#8836)

[ti-chi-bot]

This is an automated cherry-pick of #8836

What problem does this PR solve?

Issue Number: close #8824

What is changed and how it works?

Hide fields that are not required for specific protocols and downstream types. Since we utilize a common changefeed configuration template, certain fields may not be utilized for certain protocols.

Check List

Tests

• Manual test (add detailed scripts or steps below)
  Execute a manual test on a TiDB cluster generated with TiUP playground, and include a partial output of the cdc cli changefeed query command. The output has been modified to exclude any unnecessary fields, such as csv and schema_registry, as well as other fields that are not utilized.

{
  "upstream_id": 7225670347271394026,
  "namespace": "default",
  "id": "simple-replication-task",
  "sink_uri": "kafka://127.0.0.1:9092/quickstart-events?protocol=canal-json",
  "config": {
    "memory_quota": 1073741824,
    "case_sensitive": true,
    "enable_old_value": true,
    "force_replicate": false,
    "ignore_ineligible_table": false,
    "check_gc_safe_point": true,
    "enable_sync_point": false,
    "bdr_mode": false,
    "sync_point_interval": 600000000000,
    "sync_point_retention": 86400000000000,
    "filter": {
      "rules": [
        "*.*"
      ],
      "event_filters": null
    },
    "mounter": {
      "worker_num": 16
    },
    "sink": {
      "protocol": "canal-json",
      "transaction_atomicity": "",
      "encoder_concurrency": 16,
      "terminator": "\r\n",
      "date_separator": "none",
      "enable_partition_separator": true,
      "enable_kafka_sink_v2": false,
      "only_output_updated_columns": false
    },
    "consistent": {
      "level": "none",
      "max_log_size": 64,
      "flush_interval": 2000,
      "storage": "",
      "use_file_backend": false
    },
    "scheduler": {
      "enable_table_across_nodes": false,
      "region_threshold": 100000,
      "write_key_threshold": 0
    },
    "integrity": {
      "integrity_check_level": "none",
      "corruption_handle_level": "warn"
    }
  },
  "create_time": "2023-04-24 10:33:13.965",
  "start_ts": 441019949069107204,
  "resolved_ts": 441019961560268803,
  "target_ts": 0,
  "checkpoint_tso": 441019961560268803,
  "checkpoint_time": "2023-04-24 10:34:01.450",
  "state": "normal",
  "creator_version": "v7.1.0-master-dirty",
  "task_status": [
    {
      "capture_id": "90d43a75-9047-4b3f-a7ab-37e6a3bff357",
      "table_ids": [],
      "table_operations": null
    }
  ]
}

Questions

N/A

Will it cause performance regression or break compatibility?

N/A

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

N/A

Release note

`None`

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[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	3b5185c	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/test-infra repository. I understand the commands that are listed here.

[CharlesCheung96]

/hold dateSeperate should be set to day

[charleszheng44]

/cherry-pick-invite

[ti-chi-bot]

@charleszheng44 you're already a collaborator in repo ti-chi-bot/tiflow

[ti-chi-bot]

PR needs rebase.

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/test-infra repository.

[nongfushanquan]

/close

[ti-chi-bot]

@nongfushanquan: Closed this PR.

In response to this:

/close

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/test-infra repository.