Description

Add support for "generic binding".
"In the service catalog UX this meant I just want the information dumped into a Secret, and then I'll choose what to do with it after that. This is good for referencing the Secret from other things like Jobs, or a Tekton pipeline, where your controller may not be able to directly modify a pod spec.
 
The request for this is coming up in discussions about transitioning some IBM brokers off of service catalog to operators instead. I think the use case is valid so we should consider it."

Acceptance Criteria

1. If the `ApplicationSelectors` is skipped, only the binding secret should be created with the name of the secret being dumped in the status for arbitrary consumption.
2. If the CR is updated with the `ApplicationSelectors` section, then the controller should inject the previously created secret into the deployment/deploymentconfig.
3. Irrespective of (2), If the credentials change on the backing service side, the binding secret should be updated as well - as per enhancement in https://jira.coreos.com/browse/ODC-1558