Backport of Dashboard TLS Configuration Details Bug into release/1.15.x

[hc-github-team-secure-vault-core]

Backport

This PR is auto-generated from #23726 to be assessed for backporting due to the inclusion of the label backport/1.15.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@zofskeez
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/vault/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

The TLS field of the configuration details section on the dashboard was not displaying accurately based on the configuration settings. Since the tls_disable default value is false, it doesn't need to be defined and could be missing from the configuration. In addition, when using TLS the tls_cert_file and tls_key_file values are required. I updated to check that tls_disable is either undefined or false and both file properties have value to determine if TLS is enabled.

The screen shot below is after the changes with the following config:

api_addr = "https://127.0.0.1:8200"
disable_mlock = true

listener "tcp" {
  address = "127.0.0.1:8200"
  tls_cert_file = "./certs/vault-cert.pem"
  tls_key_file = "./certs/vault-key.pem"
}

storage "inmem" {}

I also noticed when running a dev server that it was incorrectly reporting that TLS was Enabled which is now showing Disabled as expected.

---

Overview of commits

• a31b029

[hashicorp-cla]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[github-actions]

CI Results:
Failures:

Test Type	Package	Test	Logs
	builtin/logical/pkiext/pkiext_binary	Test_ACME	view test results
	builtin/logical/pkiext/pkiext_binary	Test_ACME/group	view test results
	builtin/logical/pkiext/pkiext_binary	Test_ACME/group/caddy_http	view test results
	builtin/logical/pkiext/pkiext_binary	Test_ACME/group/caddy_http_eab	view test results
	builtin/logical/pkiext/pkiext_binary	Test_ACME/group/caddy_tls-alpn	view test results