Allow SSL Context Service to be configured for Registry Clients

[ChrisSamo632]

Is your feature request related to a problem?

NiFi Registry Clients deployed by NiFiKop cannot connect to secured NiFi Registry instances without manual intervention.

Describe the solution you'd like to see

An optional SSL Context Service should be allowed to be configured along with the NiFi Registry Client when deployed through NiFiKop.

This should allow for the different types of Controller Service (including the newer PEM context) and should be configurable with one/both of:

• certificates controlled by NiFiKop as part of a NiFi Cluster
• additional certificates specified by the user

Describe alternatives you've considered

• Manually configuring the SSL Context Service within the deployment
• Using NiFi Toolkit/NiPyApi to script the connectivity as part of a post-deployment Job

Additional context

No response

[juldrixx]

It seems fair to have this issue, but maybe it could be intersting to think of a way to do it with #509 at the same time.

[ChrisSamo632]

It seems fair to have this issue, but maybe it could be intersting to think of a way to do it with #509 at the same time.

I agree that #509 may present a better/more general approach, but figured it was sensible to include this too in case there's a more immediate need/it's simpler for someone in the community to do at some point