Feature - End User-Controlled client connection for remote access

[MartyEwings]

Make an outward authenticated connection to a Puppet hosted endpoint. The instantiation and duration should be controlled by the customer.

Purpose

To facilitate command line access to the customer RSAN node by remote Puppet Support engineers.

Assumptions

Connecting to an OpenVPN endpoint in the Puppet Office
Authentication using existing unique identifier on the PE install, the Licence Key OID

Not doing

Individual user logon identification
Acceptance criteria
Deployment of a suitable client and configuration
PreShared Key authentication using PE license UUID
Facility for the customer to control when the RSAN node connects to Puppet
Configurable session durations for the connection to Puppet
Control should be possible from built-in Puppet Enterprise functionality
Deployment of the client should be optional
Optional vpn enable script ON RSAN node incase PE infra down

[MartyEwings]

Branch openvpn contains the first STAB at this feature, a package resource and a defined type to set up client config for the connection.
This is largely on hold until we can do test connections with IT infrastructure.

[MartyEwings]

@jordi-garcia do you have any code you can check into a branch?