Fix mTLS Configuration for Karmada Scheduler & Descheduler Components

[jabellard]

What type of PR is this?
/kind bug

What this PR does / why we need it:

A recent change introduced new flags for configuring mTLS for the Karmada Scheduler & Descheduler components. As such, the manifest templates for those components were changed accordingly to reflect the new change. Configuration of the new flags now require that a volume be mounted to use as the source of the TLS data. However, it looks like there's one more change required that was missed.

Which issue(s) this PR fixes:
Fixes #5545

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

`karmada-operator`: Fixed the issue where the manifests for the `karmada-scheduler` and `karmada-descheduler` components were not parsed correctly.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

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

Project coverage is 34.13%. Comparing base (2e60a6e) to head (24d9e12).

Files with missing lines	Patch %	Lines
operator/pkg/controlplane/controlplane.go	0.00%	22 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5546      +/-   ##
==========================================
- Coverage   34.14%   34.13%   -0.01%     
==========================================
  Files         643      643              
  Lines       44509    44511       +2     
==========================================
- Hits        15197    15196       -1     
- Misses      28156    28159       +3     
  Partials     1156     1156              

Flag	Coverage Δ
unittests	34.13% <0.00%> (-0.01%)	⬇️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[chaosi-zju]

seems like same PR as #5519

@zhzhuang-zju

[zhzhuang-zju]

seems like same PR as #5519

@zhzhuang-zju

Yeah, We try to fix this issue in #5519; you can track it there @jabellard .

[RainbowMango]

/lgtm
/approve

We can have both of them.

@jabellard I added a release note on this PR and we will backport this to release-1.11.

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RainbowMango

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:

• operator/OWNERS [RainbowMango]

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