Improve DS8 Communications Certificate Renewal Process

The current Communication Certificate renewal process is lengthy and cumbersome, and as the industry is moving over the next few years to require rotating certificates every 47 days vs just once a year, improving existing workflows as much as possible will be important to reducing administrative overhead. Currently we need to:

1. Submit a certificate signing request on HMC1
2. Take that CSR and get it signed by our CA
3. Download the signed certificate
4. Import that certificate back into HMC1
5. HMC1 will then reboot which can take 15-20 minutes before it is 100% ready for use again.
6. Repeat for HMC2

Would recommend some opportunities for streamlining this process:

1. Primarily, allow for installation of the new communications certificate without requiring a complete HMC reboot. Most other platforms including IBM offerings allow for certificate renewals with only a momentary restart of the management services.
2. Allow for importing certificates generated on the CA vs requiring it to be a CSR process.
3. Allow for the use of a single communications certificate to be installed for each HMC, for example like with the Storwize platforms we don't need a separate certificate for each node in the system even though each one has their own management interface.
4. Provide automation opportunities to the certificate renewals process, for example via API or Ansible modules.