[Kafka] Make all the remaining SSL fields configurable via Fleet UI

[devamanv]

Proposed commit message

See title

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

How to test this PR locally

• Run elastic-package test pipeline -v to verify that all tests pass
• Install the Kafka integration and configure the SSL fields from the Fleet UI
• Verify that the fields are present in the policy and their values

Related issues

• Closes [Kafka] Add YAML boxes for the missing SSL related fields #8227

Screenshots

Verified that SSL fields are present in the Agent policy and have the correct values as entered while installing the package

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-06T09:16:49.502+0000

• Duration: 15 min 3 sec

Test stats 🧪

Test	Results
Failed	0
Passed	20
Skipped	0
Total	20

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	100.0% (1/1)	💚
Classes	100.0% (1/1)	💚
Methods	72.222% (13/18)	❕
Lines	78.082% (57/73)	❕
Conditionals	100.0% (0/0)	💚

[milan-elastic]

Can we add the title field here for all ssl.* fields based on the description here in configuration parameter? It doesn't look good on the UI with technical fields name, it should be moreover user friendly.

[shmsr]

PR looks good overall but ++ to this comment by Milan.

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[milan-elastic]

Looks good!

[shmsr]

LGTM

nit: ssl.* could be provided in advance settings too right (by setting show_user: false)? If yes, not sure changing it now is a good idea or not.

I do not know the decision behind keeping show_user: true for ssl.{key,certificate,certificate_authorities}

[devamanv]

LGTM

nit: ssl.* could be provided in advance settings too right (by setting show_user: false)? If yes, not sure changing it now is a good idea or not.

I do not know the decision behind keeping show_user: true for ssl.{key,certificate,certificate_authorities}

@shmsr before this change, we already had a couple of ssl fields with show_user: true, I just added the missing ones. That's why didn't change the behavior. No other reason. If you feel they should all be hidden, please let me know and. I will make the change.

[elasticmachine]

Package kafka - 1.11.0 containing this change is available at https://epr.elastic.co/search?package=kafka