Tie broker apb

[djzager]

This automates the process of building an APB that is tied directly to a specific version of the broker. This should allow for automated publishing of master, release-, and ansible-service-broker- branches to dockerhub of 1) the broker 2) broker-apb that were built at the same time.

Assuming this PR is acceptable, the consequences are:

1. A merge to master will create a new build of docker.io/ansibleplaybookbundle/origin-ansible-service-broker:canary and docker.io/automationbroker/automation-broker-apb:canary
2. A merge to release-1.3 (future) will create a build of docker.io/ansibleplaybookbundle/origin-ansible-service-broker:release-1.3 and docker.io/automationbroker/automation-broker-apb:release-1.3 (NOTE: the dockerhub registry will be configured to look at latest)
3. A merge to ansible-service-broker-1.3.2-1 (future) will create a build of docker.io/ansibleplaybookbundle/origin-ansible-service-broker:ansible-service-broker-1.3.2-1 and docker.io/automationbroker/automation-broker-apb:ansible-service-broker-1.3.2-1 (NOTE: the dockerhub registry will be configured to look at latest)

[coveralls]

Coverage remained the same at 33.435% when pulling 2e63203 on djzager:tie-broker-apb into 5efd847 on openshift:master.

[jmontleon]

ACK from me. Asked rhallisey for a review so he's aware and on board since he cares for the travis side of things. If we get this working it'd be nice to make some changes to catasb to get back the ability to deploy different broker images.

[rthallisey]

ack from me