Orchestration of LASR private TLS CA

[mattgeddes]

For some services between LASR nodes, we'll need support for TLS certificates. These should be signed by a CA, but don't need to signed by a public CA. The simplest approach here might be to reuse some of @mattgeddes ' existing code to deploy a Versatus CA, and to then have all the nodes trust it, and to generate a Versatus certificate for each node. That will allow any Versatus alphanet services to be able to use TLS to communicate with services on any other Versatus alphanet machine. This could apply to Prometheus, MongoDB, Nginx, Kubo, and any other services that are used within the LASR alphanet network.