Goal:

• Provide a way to deploy a standalone (aka external) Capsule
• Deploying Capsules (= additional systems that expose Satellite features to a sub-set of client systems) is a crucial feature of a Satellite deployment.
  The "Installing Capsule Server" guide at https://docs.redhat.com/en/documentation/red_hat_satellite/6.18/html-single/installing_capsule_server/index describes the current deployment

Acceptance Criteria:

• a certificate bundle for Capsule operation can be created using foremanctl on the Satellite server
• the Capsule deployment workflow can consume said bundle to enable authentication with the Satellite server
• the Capsule is registered in the Satellite server
• Pulp is deployed in "mirror" mode to allow clients to consume content
• any feature that has a "smart proxy" component (rex, ansible, etc) can be enabled and properly configured on a Capsule
• Documentation is updated to reflect the changes in tooling/deployment style
• Tests are updated to reflect the changes in tooling/deployment style

Open questions:

• Do we still need --foreman-proxy-dhcp-ping-free-ip
• How do we handle container distribution to the capsule? Same as RPM (register to Satellite, consume content from there)?