[Fleet] Fix output ca_trusted_fingerprint validation message

[nchaulet]

Summary

Update the validation message for the output ca_trusted_fingerprint to remove the mention of base64 encoded that was not correct at all.

UI Changes

Questions

It is not easy for the users to find the info on how to generate the fingerprint should we add something directly in the UI like this?

@karenzone @insukcho what do you think?

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[apmmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 8d49463

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
fleet	942.2KB	942.2KB	+15.0B

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
securitySolution	433	436	+3

Total ESLint disabled count

id	before	after	diff
securitySolution	513	516	+3

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @nchaulet

[kpollich]

Code LGTM - I like the idea of having a better explanation of what we're expecting here too with a shell example or maybe a link to some docs. I'll let some tech writing folks weigh in on specifics.

[insukcho]

LGTM, too! Sorry for the late response. Also totally agree to add more specific guidelines in the UI. Thanks!