[ENHANCEMENT] In Harvester Installer pkg/console/install_panels.go show DNS Servers User Input within func addConfirmInstall Panel

[irishgordo]

Is your enhancement related to a problem? Please describe.
A user, can't, at the final stage see DNS Servers that they input

Describe the solution you'd like
func addConfirmInstallPanel could possibly just show that information

Describe alternatives you've considered
A user, just "has to remember" what they input for that field...

Additional context
A user is being asked for DNS servers, or default is used, if the user inputs DNS servers, showing the user the DNS servers they input on the final panel could be beneficial for a multitude of reasons.

[harvesterhci-io-github-bot]

added backport-needed/1.3.1 issue: #5702.

[harvesterhci-io-github-bot]

added backport-needed/1.2.2 issue: #5703.

[harvesterhci-io-github-bot]

Pre Ready-For-Testing Checklist

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

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

• Install Harvester.
• Add DNS servers.
• The DNS server should display in the final review panel:

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

• Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)?
  The PR 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:

• If labeled: area/ui Has the UI issue filed or ready to be merged?
  The UI issue/PR is at:

• If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?
  The documentation/KB PR is at:

• If NOT labeled: not-require/test-plan Has the e2e 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?

  • The automation skeleton PR is at:
  • The automation test case PR 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:

[bk201]

@irishgordo I added a test plan and moved the issue to ready for testing. Thanks.

[noahgildersleeve]

I accidentally closed this when I was testing the backport issue with #5703 . So I'm marking it as ready for testing again.