A little more thoughts now that I have some headspace.

UPS has an apb we use (https://github.com/aerogearcatalog/unifiedpush-apb/blob/master/apb.yml) which has binding parameters. We are wanting to have the binding the user does in MDC to specify which variant they are configuring, but this isn't how bindings want to work under the hood. What we will need to do is remove the Client_type parameter and upgrade the operator to be able to check the provided binding parameters for which platforms(s) the user is configuring.

Here is why :
APB binding parameters are processed by OpenShift into a schema. This shema is used to generate the forms that the user sees. Because we want each binding to be a subset of the parameters that we are asking for, we now "need" multiple bindings and also have to handle the form differently from every other form openshift will ever show us. Because of how deep the assumption of "one binding form per apb" is, we can't have the client type be a field. Each binding for UPS must be the whole state of an applicaiton's binding for UPS, otherwise we have to handle each binding we will ever want to do in MDC as if it were a special snowflake instead of relying on the generic patterns openshift provides.