To accommodate cloud provider specifics, leapp's internal RHUI handling infrastructure provides a lot of flexibility that is auto configured on runtime. However, this auto configuration can be problematic if the cloud provider introduces changes that the auto configuration code does not accounts for.

This task, therefore, requests using the newly introduced IPU configurability to allow overriding leapp's internal RHUI mechanism. The user should be able to:

1. provide essentially an entire RHUI_SETUP entry that will be used by leapp and the autoconfiguration will be skipped
2. decide whether the target client should be bootstrapped or whether the bootstrapping process is to be skipped