Backport of docs: Clarify credential workflow for SSH target types into release/0.17.x

[hc-github-team-secure-boundary]

Backport

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

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

---

The documentation is not clear about the requirement to use injected credentials for SSH target types. This has led to some confusion internally. This PR attempts to connect some dots between target type requirements and the credential brokering/injection workflows.

It contains the following updates:

• In the Credential injection section of the Credential management concepts page, I changed "Credential injection is available..." to "Credential injection is required..."
• In the End user workflows section of the credential management Overview topic, I added a 4th paragraph that explains that target type has an impact on the credential workflow you can configure.
• In the Requirements section of the credential brokering configuration topic, I updated the first bullet to add "To use brokered credentials to connect to a target that runs SSH, you must use a TCP target type. I also added a More information section at the bottom of the topic.
• In the Requirements section of the credential injection configuration topic, I updated the second bullet to add "To use injected application credentials to connect to a target that runs SSH, you must use an SSH target type. I also added a More information section at the bottom of the topic.

---

Overview of commits

• ba0c53f

• 13c6160

• 85070b0