Backport of docs: Fixes examples for alias_refresh_interval & dns_request_timeout into release/0.19.x

[hc-github-team-secure-boundary]

Backport

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

🚨

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:
@johanbrandhorst
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/boundary/merges: 409 Merge conflict []

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

---

• Issue: Client agent does not start if the given example configurations are used.
• Both the parameters are parsed using parseutil.ParseDurationSecond, which parses a duration from a string or numeric value into a time.Duration.
• When units are missing (such as when a numeric type is provided), the duration is assumed to be in seconds.
• Since providing a time format is more readable, updating the example to the corrected string version.
• Providing a string example configuration is more suitable than providing a number example like alias_refresh_interval=60; where it is automatically assumed to be seconds, and can become confusing for the consumers.

---

Overview of commits

• 0c73172

• 35f2ce3

[hashicorp-cla-app]

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 have already 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.}

[hashicorp-cla-app]

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 have already 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.}

[johanbrandhorst]

CC @stellarsquall same question about this PR, what does it mean to backport the docs?

[stellarsquall]

the backport/website label is supposed to merge the commit into the latest release branch and the stable-website branch. This ensures that the change goes live immediately, and that its available in the version picker when a subsequent release is published.

The runners have been working just fine, but I've never commented on one of these auto-generated PRs, so I'm not sure what will happen. We can manually merge them though if the action fails

[johanbrandhorst]

OK cool I'll manually merge these

[johanbrandhorst]

Superceded by #5548