dm: fix start task check when both shard-mode and TLS are configured (#11843)

[ti-chi-bot]

This is an automated cherry-pick of #11843

What problem does this PR solve?

When task configuration contains both shard-mode and TLS configuration, start task fails

Issue Number: close #11842

What is changed and how it works?

The content of the task configuration file is replaced with the TLS context populated when TLS configuration exists. The changed configuration file content generates false positives in the pre-checking logic. Reordering the pre-checking and loading of the TLS context can make it work in such cases.

Check List

Tests

• 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

None

[ti-chi-bot]

This cherry pick PR is for a release branch and has not yet been approved by triage owners.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

1. It must be approved by the approvers firstly.
2. AFTER it has been approved by approvers, please wait for the cherry-pick merging approval from triage owners.

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.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-8.5@d8f0a6e). Learn more about missing BASE report.

Additional details and impacted files

Components	Coverage Δ
cdc	59.6437% <0.0000%> (?)
dm	50.0577% <0.0000%> (?)
engine	53.2336% <0.0000%> (?)

Flag	Coverage Δ
unit	55.1660% <0.0000%> (?)

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

@@               Coverage Diff                @@
##             release-8.5     #11863   +/-   ##
================================================
  Coverage               ?   55.1660%           
================================================
  Files                  ?       1002           
  Lines                  ?     136575           
  Branches               ?          0           
================================================
  Hits                   ?      75343           
  Misses                 ?      55726           
  Partials               ?       5506           

[sunxiaoguang]

/retest

[sunxiaoguang]

/retest

[sunxiaoguang]

/retest

[sunxiaoguang]

/retest

[Benjamin2037]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Benjamin2037

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:

• dm/OWNERS [Benjamin2037]

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

[sunxiaoguang]

/retest

[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
pull-dm-integration-test	30c4fb8	link	true	/test dm-integration-test

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.