[BUG] The wrong template in default-setting.yaml of the Longhorn chart in v1.5 and v1.4

[mantissahz]

Describe the bug (🐛 if you encounter this issue)

The wrong template in the default-setting.yaml file such as https://github.com/longhorn/longhorn/blob/v1.5.x/chart/templates/default-setting.yaml#L49-L57.
That will make the field data of the ConfigMap longhorn-default-setting get the wrong data format.
Or get the unexpected result by running the script longhorn/scripts/generate-longhorn-yaml.sh.

Expected behavior

Generate the correct data from longhorn/chart/templates/default-setting.yaml file

Additional context

[innobead]

@mantissahz self assign and assign to the milestone directly next time.

[longhorn-io-github-bot]

Pre Ready-For-Testing Checklist

• Where is the reproduce steps/test steps documented?
  The reproduce steps/test steps are at:

1. Customize some values of the defaultSettings in chart/values.yaml
2. Install Longhorn with chart/values.yaml by Helm
3. Install successfully and default settings as expected.

• Is there a workaround for the issue? If so, where is it documented?
  The workaround is at:

• Does the PR include the explanation for the fix or the feature?

• Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
  The PR for the YAML change is at:
  The PR for the chart change is at:
  charts: fix the default-setting cm format issue #7767

• Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)?
  The PR is at

• Which areas/issues this PR might have potential impacts on?
  Area
  Issues

• If labeled: require/LEP Has the Longhorn Enhancement Proposal PR submitted?
  The LEP PR is at

• If labeled: area/ui Has the UI issue filed or ready to be merged (including backport-needed/*)?
  The UI issue/PR is at

• If labeled: require/doc Has the necessary document PR submitted or merged (including backport-needed/*)?
  The documentation issue/PR is at

• If labeled: require/automation-e2e Has the end-to-end test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue (including backport-needed/*)
  The automation skeleton PR is at
  The automation test case PR is at
  The issue of automation test case implementation is at (please create by the template)

• If labeled: require/automation-engine Has the engine integration test been merged (including backport-needed/*)?
  The engine automation PR is at

• If labeled: require/manual-test-plan Has the manual test plan been documented?
  The updated manual test plan is at

• If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
  The compatibility issue is filed at

[roger-ryao]

Verified on v1.5.4-rc1 20240206

• longhorn v1.5.4-rc1 f838d7e

The test steps
#7459 (comment)

Result Passed

1. Install successfully and default settings as expected.