Add Tls with keystore type config support

[jiazhai]

Fixes #6640

Motivation

Add Tls with keystore type config.

Modifications

Add Tls with keystore type config.

Verifying this change

• Unit test passed

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

• Dependencies (does it add or upgrade a dependency): (yes / no)
• The public API: (yes / no)
• The schema: (yes / no / don't know)
• The default values of configurations: (yes / no)
• The wire protocol: (yes / no)
• The rest endpoints: (yes / no)
• The admin cli options: (yes / no)
• Anything that affects deployment: (yes / no / don't know)

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
• If a feature is not applicable for documentation, explain why?
• If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

[rdhabalia]

I haven't gone through with the entire change but it seems it touches many different files and I think supporting multiple CA trust stores can be done in an easier way and might not need this big change.
we can always bundle multiple CA trust store in one file and it can be provided to pulsar-broker. We also have similar kind of requirement and we are going to bundle multiple certs into one to support multiple ca usecase.
https://alvinalexander.com/java/java-using-keytool-import-certificate-keystore/
We can also add script in the repo for reference which can allow user to bundle multiple certs.

@merlimat can you also please review this PR.

[jiazhai]

@rdhabalia Thanks for the comments. The name of the PR seems be a little misleading. Changed the name to align with the main changes. It mainly want to support keystore configs. and make multi ca easy config is one result of it.
This change tries to keep the original tls settings untouched, and add new config in needed path, so it changed number of files. Maybe we could make the supporting work aligned in the future.

[rdhabalia]

I will try to review it soon

[sijie]

Overall the change looks good to me. And it is protected by the flag tlsEnabledWithKeyStore. It seems to be a safe change.

[sijie]

@jiazhai I think we need to add those settings to the configuration files and the website documentation. Can you please create an issue to follow up on a change?

[jiazhai]

Hi @rdhabalia Thanks for taking care. If this is too hurry for the review, we could handle it in the following issues and prs.