Provide a new implementation for cloud connector

[jeremylenz]

In foreman_rh_cloud to set up cloud remediations, currently

1. you have to click "Configure cloud connector" in the UI
2. this runs a "self-REX" job template (a REX job on the Foreman base system) --> https://github.com/theforeman/foreman_rh_cloud/blob/f2d29a00d9c581ddbb6865f044afd4a7a74a2d4b/app/views/job_templates/cloud_connector.erb#L4
3. this runs https://github.com/theforeman/foreman-operations-collection/tree/develop/roles/cloud_connector
4. now, the listener listens for incoming cloud remediations and when one comes in, downloads the playbook from cloud and runs it on hosts via REX Ansible.

We need an implementation of this for foremanctl that does not require a "base system". This could run in a container that advertises itself as a Smart Proxy feature.

[ehelms]

Thanks for capturing this @jeremylenz ! This is a scenario we will need to re-think on how it's implemented. In the current design, my recall is there were two factors driving the implementation:

1. We wanted to try to give users a way to manage their installation from the UI by offering a push button deployment of the tooling needed for cloud connector to operate.
2. Cloud connector needed a way to connect to Foreman with authentication and by generating an access token during configuration this could be orchestrated without an installer run.

I like where you are headed with turning this into a container itself that is configured through foremanctl and removing the UI-based approach. We would still need to solve the authentication aspect given that Cloud Connector calls APIs.