ZSS HTTPS ciphers are not user customizable

[1000TurquoisePogs]

It appears the ZSS ciphers are a default list which get maintained but are not something the user can customize.
https://github.com/zowe/zss/blob/f397363b33aa0d2e0c31201d0b2047a0750e148b/c/zss.c#L1202=

It looks like other https parameters are customized within agent.https, and so just allowing customization via agent.https.ciphers sounds good.

[1000TurquoisePogs]

Since the current list is:
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

If you wanted to set that via config, it looks like they resolve to strings https://github.com/zowe/zowe-common-c/blob/3dc9ce9855a29587618a4a37e058746bac24c5c7/h/tls.h#L40=
ciphers=009E009FC02BC02CC02FC030

[1000TurquoisePogs]

https://testssl.sh/openssl-iana.mapping.html lists the openssl and iana names of ciphers.
I suggest rather than doing

agent.https.ciphers=009E009FC02BC02CC02FC030

It would be good to have a mapping between the ints and names so that people can do

agent.https.ciphers=TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

For example.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs, but can be reopened if needed. Thank you for your contributions.

[github-actions]

This issue has been automatically closed due to lack of activity. If this issue is still valid and important to you, it can be reopened.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs, but can be reopened if needed. Thank you for your contributions.

[1000TurquoisePogs]

Implemented in v2.13.0