🐞 bug: When PITR backup, --dn-threads-num is set to 10, and the actual dn node executes “--threads=1”

[peilinqian]

Environment

• Contents of your values.yaml file,if your helm deployment process goes wrong.
• Contents of your CRD resource file. Include proxy.shardingsphere.apache.org/v1alpha1 and proxyconfig.shardingsphere.apache.org/v1alpha1
• Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version

Issue description

• Which phase is not functioning properly, is it the installation phase or the apply CRD phase ?

When PITR backup, --dn-threads-num is set to 10, and the actual dn node executes “--threads=1”

Error log

• Including ShardingSphere-Proxy error log and ShardingSphere-Operator error log

Expected result

When PITR backup, --dn-threads-num is set to 10, and the actual dn node executes “--threads=10”